Originally posted by kpedersen
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 mdedetrich View Post
[...]
But yes in short you are correct, just randomly or automatically backporting fixes from later kernel release is also in my mind inanely stupid. If you are going to backport fixes in this way thats thats fine as long as its a deliberate thought out procedure where you also test whats being back ported.
[...]
maybe there's some script option for individual review of memory, fs, storage, network or server (uptime) related patches ]
Comment
-
Originally posted by mdedetrich View Post
Thats not why people have support contracts. You don't have a support contract for 20 issues per year because you expect to fill that quota every year, its because given enough time as part of software development you end up hitting some weird issues every now and then which is why you have such a contract, so you are not caught off guard. A company like Microsoft wouldn't even be that strict on the cap, they understand that on some years you may go slightly over because of unforeseen reasons.
The whole point of these contracts is so you, as a business have someone to rely on when shit hits the fan and contacting some Linux kernel dev on the ML is no way close to that.
Comment
-
Originally posted by HEL88 View Post
1. This error did not occur on its own, but the user must have maliciously caused it.
2. It only worked locally so the user at most could have corrupted his desktop.
3. It did not cause any data loss or data corruption.
A minor bug.
And on Linux??? Secure ZFS file system scored a mega-bug, 'modern' BTRFS file system too. Apparently a million watching eyes is not enough. Probably a billion is needed, or maybe it's enough to raise salaries to bring in better specialists?
That said, these filesystems are not formally verified, so it is likely that they contain such bugs.
- Likes 1
Comment
-
Originally posted by user1 View PostTurns out, when it comes to filesystems, the most reliable setup is NTFS on Windows
But seriously, I know that Windows NT is closed source, but despite the fact that its userland may suck, I don't think the NT kernel suffers from this amount of serious regressions like Linux lately does, especially in filesystems.
I am a fellow person with zero knowledge of Microsoft’s internal discoveries in NTFS, but I assume that there are bugs both known and unknown in NTFS.
For what it is worth, misdirected writes can cause NTFS to blow up. That is a problem that affects all filesystems not able to detect corruption by the layer beneath them. It is a design flaw, not a bug, since the filesystem design assumes the block layer never does anything it should not.Last edited by ryao; 14 December 2023, 03:22 PM.
- Likes 1
Comment
-
Hello everybody,
I would like to apologize for my posts under nickname "sophisticles" and "hel88".
the thing is, I am very sick person. Schizophrenia with manic depression.
When I'm on my medication like now, I feel ashamed for the things that I do when not on medication.
For example, when I'm not using my therapy properly I get this crazy tendency to troll on linux forums. For that devious purpose I am using nicknames "sophisticles" and "hel88". under those nicknames I write crazy, insane things. when I am on regular therapy like now, I cannot believe the crap that I wrote under those 2 nicknames.
overall, I would like all of you to know that I don't really mean what I write under those 2 nicknames and also, I love linux, open source and gpl. and yes, microsoft sucks.
Comment
Comment