‘Dirty Pipe’ security patched kernels available

[Forum Admin anticapitalista]

All users that use any 5.10 kernel are strongly advised to upgrade to the latest version – 5.10.104 – in the antiX repos. This applies to 64 bit and 32 bit pae and non-pae kernels for antiX-17, antiX-19, antiX-21 and testing/sid users.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

All users that use any 5.10 kernel are strongly advised to upgrade to the latest version – 5.10.104

The latest through Package Installer appears to be still 5.10.88…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Moderator Brian Masinick]

Helpful

Up

0

::

olsztyn wrote:

anticapitalista wrote:

All users that use any 5.10 kernel are strongly advised to upgrade to the latest version – 5.10.104

The latest through Package Installer appears to be still 5.10.88…

I’m sure it’ll be there soon, if not already. Be sure you run sudo apt update before checking again. If your local repo does not have it yet, it should be there by tomorrow, if not later today.

--
Brian Masinick

[Member stevesr0]

Helpful

Up

0

::

Found the dirty pipe patched kernel 5.10.104 in the repositories just now. Installed it and after reboot, happy to note that my alsa/pipewire sound configuration works fine as with other recent antix custom kernels!

stevesr0

• This reply was modified 1 year, 1 month ago by stevesr0.
• This reply was modified 1 year, 1 month ago by stevesr0.

[Moderator christophe]

Helpful

Up

0

::

Many thanks for this.

confirmed antiX frugaler, since 2019

[Member Robin]

Helpful

Up

0

::

Many thanks, anticapitalista, for the security patched kernel upgrade.
While installing it using apt instead of GUI-packageinstaller I’ve got an error message during installation. Don’t know what to make of it, or whether it is serious or whether it’s just the usual ambient noise of kernel installation. Here the respective parts from the console output (this was a fresh install, so the recently used kernel was still 5.10.57-antix.1-amd64-smp from the ISO):

$ sudo apt-get update

  ... (everything fine here)

$ sudo apt-get install linux-image-5.10.104-antix.1-amd64-smp linux-headers-5.10.104-antix.1-amd64-smp

  ... (everything fine here)

make -j1 KERNELRELEASE=5.10.104-antix.1-amd64-smp -C /lib/modules/5.10.104-antix.1-amd64-smp/build M=/var/lib/dkms/exfat/5.9/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.104-antix.1-amd64-smp (x86_64)
Consult /var/lib/dkms/exfat/5.9/build/make.log for more information.

  ... (everything fine here)

$ cat /var/lib/dkms/exfat/5.9/build/make.log
DKMS make.log for exfat-5.9 for kernel 5.10.104-antix.1-amd64-smp (x86_64)
Mi 16. Mär 22:19:09 CET 2022
make: Verzeichnis „/usr/src/linux-headers-5.10.104-antix.1-amd64-smp“ wird betreten
  CC [M]  /var/lib/dkms/exfat/5.9/build/inode.o
In file included from /var/lib/dkms/exfat/5.9/build/exfat_fs.h:14,
                 from /var/lib/dkms/exfat/5.9/build/inode.c:16:
/var/lib/dkms/exfat/5.9/build/compat.h:12:2: error: #error "This driver doesn't support v5.8+, " "please use the included driver from your kernel"
   12 | #error "This driver doesn't support v5.8+, " \
      |  ^~~~~
/var/lib/dkms/exfat/5.9/build/inode.c: In function ‘exfat_readpages’:
/var/lib/dkms/exfat/5.9/build/inode.c:367:9: error: implicit declaration of function ‘mpage_readpages’; did you mean ‘mpage_readpage’? [-Werror=implicit-function-declaration]
  367 |  return mpage_readpages(mapping, pages, nr_pages, exfat_get_block);
      |         ^~~~~~~~~~~~~~~
      |         mpage_readpage
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:280: /var/lib/dkms/exfat/5.9/build/inode.o] Fehler 1
make: *** [Makefile:1835: /var/lib/dkms/exfat/5.9/build] Fehler 2
make: Verzeichnis „/usr/src/linux-headers-5.10.104-antix.1-amd64-smp“ wird verlassen

I’ll try to reboot into this kernel now and let you know whether it comes up irrespective of this error message.

Update:
System comes up fine with 5.10.104 after reboot.
One error message on boot screen, right at the beginning:
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.CPU0 (20200925/dspkginit-438)
(Not sure about whether it was there already with the previous 5.10 kernel version)

• This reply was modified 1 year, 1 month ago by Robin.

Windows is like a submarine. Open a window and serious problems will start.

[Author]

Posts