https://www.redhat.com/archives/dm-deve ... 00082.html
I got notified of this via Manjaro forums.
https://forum.manjaro.org/t/kernel-5-1- ... vm/88360/4
Critical bug in 5.1 kernel?
Critical bug in 5.1 kernel?
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: Critical bug in 5.1 kernel?
Ouch!
There was an issue like this a few years ago with trim and some specific Samsung ssd's: Samsung docs detail Linux TRIM bug and fix
There was an issue like this a few years ago with trim and some specific Samsung ssd's: Samsung docs detail Linux TRIM bug and fix
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."
-- Richard Feynman
-- Richard Feynman
Re: Critical bug in 5.1 kernel?
The Redhat post specifically mentions btrfs, and the Arch one LUKS/dm-crypt. Presumably not an issue otherwise. I've had a 5.1 kernel in siduction for a short time and no problems, and also no reports on siduction forums.
Re: Critical bug in 5.1 kernel?
I don't use encryption nor 5.1 kernel. But for those who do, is it an issue? I'm just raising it but have no idea if it's applicable to MX at all.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: Critical bug in 5.1 kernel?
5.1 is not even in unstable yet. siduction usually are a bit ahead as they build from upstream afaik. I'd guess it would be fixed by the time it hits Debian proper. Reported to be fixed in Arch already - https://bugs.archlinux.org/task/62693