Originally posted by V1tol
View Post
Announcement
Collapse
No announcement yet.
Debian 12.3 Delayed Due To An EXT4 Data Corruption Bug Being Addressed
Collapse
X
-
Originally posted by RealNC View Post
Ext4 is fine, Debian just happened to break it.
- Likes 7
Comment
-
Originally posted by cynic View Post
man, I was baking my own kernel when you were still in the cradle!
fact is: no filesystem is safe, even with stable distro as Debian.
and no, it doesn't matter if it is a bug of the fs itself or a wrong backport of the distro.
For the filesystem issue: Debian and Red Hat kernel maintainers (not the coders) are known to pick patches from RC's and backport to their stable branches when the fix have to be tested. Water is wet.
Reading the mail, it seems the patch was picked by mistake, and thus, the kernel was boorked and nobody noticed until it was too late.
So it's a Debian problem, in the end, not a Kernel people problem, so the damage is only in the Debian camp. Go figure.
- Likes 3
Comment
-
Originally posted by OneTimeShot View Post
LOL Back at you I guess. I regularly work closely with Microsoft devs to address issues. It's called a support contract, which you get with a Microsoft support agreement. It includes 20 support incidents a year where you talk directly to the engineers working on software an area.
Guess what: it's not just RedHat employees who are paid to fix bugs. Microsoft employees do it too.
Btw. another thing is there should be 'stable - security patches only' branch. There are sometimes hundreds of patches being backported into stable which rises concerns among some users.. I'm not sure if it was the same in the past.Last edited by Volta; 10 December 2023, 12:11 PM.
- Likes 3
Comment
-
Originally posted by stargeizer View Post
So it's a Debian problem, in the end, not a Kernel people problem, so the damage is only in the Debian camp. Go figure.
- Likes 6
Comment
-
Originally posted by Vistaus View Post
Yeah, no hate on stable distros like Debian Stable, but the mantra among those users is always that major regressions like this don't happen on stable distros, only on rolling releases.
- Likes 3
Comment
-
Originally posted by kpedersen View Post
12.3 was delayed rather than damaging anyone's data precisely *because* Debian is not a rolling release distro. I think it further strengthens the argument on which approach I would rather choose for production.
linux-image-6.1.0-14-amd64/stable 6.1.64-1 amd64
Linux 6.1 for 64-bit PCs (signed)
- Likes 7
Comment
-
Originally posted by Volta View Post
And so? It's not only Red Hat, but dozens of others including Linux kernel developers. You can have direct contact with core Linux kernel developers in case of issue (not only 20 times per year). I once had unbootable system with some Linux-rc version. And guess what? The issue was fixed in two days. Linux ecosystem development power is levels ahead of Microsoft or Apple. I wouldn't be surprised if some of the viruses from XP were still working in Windows 11. I'll have to check, because it will tell a lot about their responsibility. I've got the feeling Microsoft is only putting additional layers on top of the leaky operating system.
Btw. another thing is there should be 'stable - security patches only' branch. There are sometimes hundreds of patches being backported into stable which rises concerns among some users.. I'm not sure if it was the same in the past.
As for a "leaky operating systems"... Well I can only sat that people who speak in absolutes and generalities are guaranteed to be wrong.
Comment
-
Originally posted by stargeizer View Post
Trolling much, old 70 years guy?? (assuming you were at least 10 years old when you compille your first unix kernel... oh yeah!! that's 1963, no kernel source or even unix back then! So i assume you compille using the nice punch-cards do you? (hint: I didn't, but i saw the machines in their final days // another hint ".dir 4").
For the filesystem issue: Debian and Red Hat kernel maintainers (not the coders) are known to pick patches from RC's and backport to their stable branches when the fix have to be tested. Water is wet.
Reading the mail, it seems the patch was picked by mistake, and thus, the kernel was boorked and nobody noticed until it was too late.
So it's a Debian problem, in the end, not a Kernel people problem, so the damage is only in the Debian camp. Go figure.
what I wanted to say is this: people choosed ext4 because they think is unbreakable while, as we can see, it can break.
to the end user it has no importance if it was a kernel devel fault, a debian fault or something else.
to the end user what matters is that their filesystem may get corrupted.
- Likes 1
Comment
Comment