diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2022-05-09 21:33:25 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2022-05-10 13:30:03 +0200 |
commit | 3c08cf6792eda8b7caf0d00f330bf289a5501341 (patch) | |
tree | efedef3a81162366f1c637efbef7b1174c44d115 /README_LVM.TXT | |
parent | 2971d8428504e8fa761d9f92273abaa1357a97ee (diff) | |
download | current-3c08cf6792eda8b7caf0d00f330bf289a5501341.tar.gz current-3c08cf6792eda8b7caf0d00f330bf289a5501341.tar.xz |
Mon May 9 21:33:25 UTC 202220220509213325_15.0
patches/packages/linux-5.15.38/*: Upgraded.
These updates fix various bugs and security issues.
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
For more information, see:
Fixed in 5.15.27:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0742
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24958
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0494
Fixed in 5.15.28:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23038
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23039
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23960
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23036
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23037
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0001
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0002
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23041
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23040
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23042
Fixed in 5.15.29:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1199
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27666
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1011
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0995
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0854
Fixed in 5.15.32:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1015
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26490
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1048
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1016
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28356
Fixed in 5.15.33:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28390
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0168
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1158
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1353
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1198
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28389
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28388
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1516
Fixed in 5.15.34:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1263
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29582
Fixed in 5.15.35:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1204
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1205
Fixed in 5.15.37:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0500
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23222
(* Security fix *)
Diffstat (limited to 'README_LVM.TXT')
-rw-r--r-- | README_LVM.TXT | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/README_LVM.TXT b/README_LVM.TXT index 93aa4e423..85b894a9f 100644 --- a/README_LVM.TXT +++ b/README_LVM.TXT @@ -103,9 +103,9 @@ We are going to 'chroot' into our fresh installation: Next, while we are in the chroot, create the initrd with LVM support -
in the example command line I assume that the root filesystem is 'ext4',
we used the LV '/dev/myvg/root' as the root device, and are running the
-Slackware 14.2 default kernel '4.4.14':
+Slackware 15.0 default kernel '5.15.19':
- # mkinitrd -c -k 4.4.14 -m ext4 -f ext4 -r /dev/myvg/root -L
+ # mkinitrd -c -k 5.15.19 -m ext4 -f ext4 -r /dev/myvg/root -L
The resulting initrd image will be written to the file '/boot/initrd.gz'
by default. We still need to tell lilo about this initrd, so open the
@@ -117,7 +117,7 @@ filename added by 'liloconfig' is '/boot/vmlinuz' which is a symbolic link to the huge SMP kernel. Remember that we need a 'generic' kernel with the initrd.
The end result should look somewhat like this:
- image = /boot/vmlinuz-generic-4.4.14
+ image = /boot/vmlinuz-generic-5.15.19
initrd = /boot/initrd.gz
root = /dev/myvg/root
label = linux
|