https://fulda.social/@Ganneff/111551628003050712
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
The new kernel release is reported to contain an ext4 data
corruption bug. It's prudent not to upgrade, or if you have
started to upgrade, not to reboot, until a new kernel release
is prepared.
The new kernel release is reported to contain an ext4 data
corruption bug. It's prudent not to upgrade, or if you have
started to upgrade, not to reboot, until a new kernel release
is prepared.
If you upgraded this morning, then I would expect that you are okay
for now.
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.
I just upgraded to Bookworm this morning. I did reboot a couple of
times but there seems to be no problem (yet). Is there anything I
should look for or do other than rebooting?
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.
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)
On 9 Dec 2023 20:54 +0200, from alexis@nanoid.net (Alexis Grigoriou):
I just upgraded to Bookworm this morning. I did reboot a couple of
times but there seems to be no problem (yet). Is there anything I
should look for or do other than rebooting?
If you upgraded this morning, then I would expect that you are okay
for now.
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. If you are on 6.1.55-1 (or earlier), just hold off on upgrades for now; and if you need to upgrade something else, take
great care for now to ensure that no Linux kernel packages get
upgraded to any version < 6.1.66, and preferably not < 6.1.66-1.
For versions, check:
* uname -v
* dpkg -l linux-image-\*
In that bug report thread, #21 lists 6.1.66 as fixed upstream, and #28 indicates that 6.1.66-1 includes the fix from upstream, and that it is
being published.
If you are on 6.1.55-1 (or earlier), just hold off on
upgrades for now; and if you need to upgrade something else, take
great care for now to ensure that no Linux kernel packages get
upgraded to any version < 6.1.66, and preferably not < 6.1.66-1.
On 9 Dec 2023 20:54 +0200, from alexis@nanoid.net (Alexis Grigoriou):
I just upgraded to Bookworm this morning. I did reboot a couple ofIf you upgraded this morning, then I would expect that you are okay
times but there seems to be no problem (yet). Is there anything I
should look for or do other than rebooting?
for now.
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. If you are on 6.1.55-1 (or earlier), just hold off on upgrades for now; and if you need to upgrade something else, take
great care for now to ensure that no Linux kernel packages get
upgraded to any version < 6.1.66, and preferably not < 6.1.66-1.
For versions, check:
* uname -v
* dpkg -l linux-image-\*
In that bug report thread, #21 lists 6.1.66 as fixed upstream, and #28 indicates that 6.1.66-1 includes the fix from upstream, and that it is
being published.
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
Andy
(amacater@debian.org)
On 2023-12-09 14:18, Michael Kjrling wrote:
On 9 Dec 2023 20:54 +0200, from alexis@nanoid.net (Alexis Grigoriou):
I just upgraded to Bookworm this morning. I did reboot a couple ofIf you upgraded this morning, then I would expect that you are okay
times but there seems to be no problem (yet). Is there anything I
should look for or do other than rebooting?
for now.
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. If you are on 6.1.55-1 (or earlier), just hold off on upgrades for now; and if you need to upgrade something else, take
great care for now to ensure that no Linux kernel packages get
upgraded to any version < 6.1.66, and preferably not < 6.1.66-1.
For versions, check:
* uname -v
* dpkg -l linux-image-\*
In that bug report thread, #21 lists 6.1.66 as fixed upstream, and #28 indicates that 6.1.66-1 includes the fix from upstream, and that it is being published.
Any idea when the fixed version will hit stable? With headless servers, it's a pain to downgrade to a previous kernel version.
On 2023-12-10, Andrew M.A. Cater <amacater@einval.com> wrote:
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
You mean in the Zulu Time Zone (as I am all at sea)?
Andy
(amacater@debian.org)
On Sun, Dec 10, 2023 at 05:09:15PM -0000, Curt wrote:
On 2023-12-10, Andrew M.A. Cater <amacater@einval.com> wrote:
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
You mean in the Zulu Time Zone (as I am all at sea)?
Andy
(amacater@debian.org)
Not this again :) GMT (was) the world standard reference point from 1884
and the Washington Conference (or thereabouts).
For most purposes GMT +0000 == UTC (or UCT if you're Francophone) ==
On 2023-12-10, Andrew M.A. Cater <amacater@einval.com> wrote:
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
You mean in the Zulu Time Zone (as I am all at sea)?
This fails with leap seconds, potentially, and also TAI astronomical
time seems to be its own animal.
On Sun, Dec 10, 2023 at 05:09:15PM -0000, Curt wrote:
On 2023-12-10, Andrew M.A. Cater <amacater@einval.com> wrote:Use "date -u" to see current UTC time. That should be sufficient to
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023You mean in the Zulu Time Zone (as I am all at sea)?
let you know how long it has been since Andrew's "now".
On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote:
On 2023-12-09 14:18, Michael Kjörling wrote:Give them a little while: release team are working on it right now as I type
On 9 Dec 2023 20:54 +0200, from alexis@nanoid.net (Alexis Grigoriou):Any idea when the fixed version will hit stable? With headless servers, it's >> a pain to downgrade to a previous kernel version.
I just upgraded to Bookworm this morning. I did reboot a couple ofIf you upgraded this morning, then I would expect that you are okay
times but there seems to be no problem (yet). Is there anything I
should look for or do other than rebooting?
for now.
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. If you are on 6.1.55-1 (or earlier), just hold off on
upgrades for now; and if you need to upgrade something else, take
great care for now to ensure that no Linux kernel packages get
upgraded to any version < 6.1.66, and preferably not < 6.1.66-1.
For versions, check:
* uname -v
* dpkg -l linux-image-\*
In that bug report thread, #21 lists 6.1.66 as fixed upstream, and #28
indicates that 6.1.66-1 includes the fix from upstream, and that it is
being published.
I'm fairly sure they're pushing it out more or less immediately once they're sure that it's built correctly and synced to all the appropriate places to
be further synced to mirrors
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
Andy
(amacater@debian.org)
On 2023-12-10 12:24, Greg Wooledge wrote:
On Sun, Dec 10, 2023 at 05:09:15PM -0000, Curt wrote:You're getting too complicated. The date stamp on his e-mail will
On 2023-12-10, Andrew M.A. Cater <amacater@einval.com> wrote:Use "date -u" to see current UTC time. That should be sufficient to
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023You mean in the Zulu Time Zone (as I am all at sea)?
let you know how long it has been since Andrew's "now".
display the correct local time (as you have set it) so I can see that he wrote it 30 minutes ago. That relative time is universal across time zones.
On Sun, Dec 10, 2023, 12:47 PM Curt <curty@free.fr> wrote:[...]
It is the notion of simultaneity itself (the now of now) that is
relative rather than universal.
I thought metaphysics was off-topic for this group. Moderators!! :-)
https://fulda.social/@Ganneff/111551628003050712
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
The new kernel release is reported to contain an ext4 data
corruption bug. It's prudent not to upgrade, or if you have
started to upgrade, not to reboot, until a new kernel release
is prepared.
-dsr-
On Sat, 9 Dec 2023 13:09:23 -0500
Dan Ritter <dsr@randomstring.org> wrote:
https://fulda.social/@Ganneff/111551628003050712
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
The new kernel release is reported to contain an ext4 data
corruption bug. It's prudent not to upgrade, or if you have
started to upgrade, not to reboot, until a new kernel release
is prepared.
-dsr-
It appears the new, repaired, kernel and minor version of Bookworm have landed. Now, who wants to live dangerously? :-)
root@tiassa:~# apt update
Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 Packages [8,787 kB] Get:4 http://deb.debian.org/debian bookworm/main Translation-en [6,109 kB] Fetched 15.1 MB in 3s (4,432 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
38 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'http://deb.debian.org/debian bookworm InRelease' changed its 'Version' value from '12.3' to '12.4'
root@tiassa:~# apt list --upgradable
Listing... Done
…
libudev1/stable 252.19-1~deb12u1 amd64 [upgradable from: 252.17-1~deb12u1] linux-image-amd64/stable 6.1.66-1 amd64 [upgradable from: 6.1.55-1] linux-libc-dev/stable 6.1.66-1 amd64 [upgradable from: 6.1.55-1]
…
root@tiassa:~#
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I assume this is the fixed version.
https://fulda.social/@Ganneff/111551628003050712
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
The new kernel release is reported to contain an ext4 data
corruption bug. It's prudent not to upgrade, or if you have
started to upgrade, not to reboot, until a new kernel release
is prepared.
-dsr-
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 32:57:47 |
| Calls: | 6,669 |
| Calls today: | 1 |
| Files: | 12,216 |
| Messages: | 5,338,282 |