Re: IMPORTANT: do NOT upgrade to new stable point release

[Richmond <dnomhcir@gmx.com>]

Greg Wooledge <greg@wooledge.org> writes:

> On Sat, Dec 09, 2023 at 07:18:20PM +0000, Michael Kjörling wrote:
>> If you upgraded this morning, then I would expect that you are okay
>> for now.
>
> That doesn't appear to be true.
>
>> Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
>> the bug is present in kernel Debian package version 6.1.64-1. If you
>> are on 6.1.55-1 (current Bookworm stable per last night) you _likely_
>> aren't affected.
>
> This is the kernel I got this morning:
>
> ii linux-image-6.1.0-14-amd64 6.1.64-1 amd64 Linux 6.1 for 64-bit PCs
> (signed)
>
> This is the current result of looking for a newer one:
>
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> Based on the warnings given here, I rebooted to the prior kernel:
>
> unicorn:~$ uname -a Linux unicorn 6.1.0-13-amd64 #1 SMP
> PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux
>
> I guess I'll wait and see what happens next.

I upgraded some time today to a December kernel. I have now gone back to
September 29 kernel. But is there a way to tell what if anything got
corrupted? I am using a 32 bit system and ext4.

I booted this:

 6.1.0-13-686-pae #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29)
 i686 GNU/Linux

then:

aptitude remove linux-image-6.1.0-14-686-pae