diff --git a/SPECS/microcode_ctl.spec b/SPECS/microcode_ctl.spec index bebec75..205b130 100644 --- a/SPECS/microcode_ctl.spec +++ b/SPECS/microcode_ctl.spec @@ -12,7 +12,7 @@ Summary: CPU microcode updates for Intel x86 processors Name: microcode_ctl Version: %{intel_ucode_version} -Release: 1%{?dist} +Release: 2%{?dist} Epoch: 4 License: CC0 and Redistributable, no modification permitted URL: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files @@ -323,7 +323,7 @@ install -m 644 "%{SOURCE182}" "%{tgl_inst_dir}/disclaimer" # send the message to syslog, so it gets recorded on /var/log if [ -e /usr/bin/logger ]; then - %{check_caveats} -m -d | /usr/bin/logger -p syslog.notice -t DISCLAIMER + %{check_caveats} -m -d | /usr/bin/logger -p syslog.warning -t DISCLAIMER fi # also paste it over dmesg (some customers drop dmesg messages while # others keep them into /var/log for the later case, we'll have the @@ -434,7 +434,7 @@ rpm -qa --qf "${qf}" ${pkgs} | sort -r -n -k'3,3' | { done if [ -n "${skipped}" ]; then - skip_msg="After installation of a new version of microcode_ctl package, + skip_msg="<4>After installation of a new version of microcode_ctl package, initramfs hasn't been re-generated for all the installed kernel packages. The following kernel packages have been skipped:${skipped}. Please re-generate initramfs manually for these kernel packages with the @@ -443,7 +443,7 @@ Intel CPU microcode included into early initramfs image for it, if needed." if [ -e /usr/bin/logger ]; then echo "${skip_msg}" | - /usr/bin/logger -p syslog.notice -t microcode_ctl + /usr/bin/logger -p syslog.warning -t microcode_ctl fi if [ -e /dev/kmsg ]; then @@ -548,6 +548,10 @@ rm -rf %{buildroot} * Wed Mar 15 2023 MSVSphere Packaging Team - 20220809-1 - Rebuilt for MSVSphere 9.1. +* Tue Oct 25 2022 Eugene Syromiatnikov - 4:20220809-2 +- Change the logger severity level to warning to align with the kmsg one + (#2136506). + * Tue Aug 09 2022 Eugene Syromiatnikov - 4:20220809-1 - Update Intel CPU microcode to microcode-20220510 release, addresses CVE-2022-21233 (#2115663):