Critical bug in 5.1 kernel?

Message

#1 Post by **asqwerth** » Wed May 22, 2019 5:22 am

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

#2 Post by **BitJam** » Wed May 22, 2019 5:32 am

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

#3 Post by **sunrat** » Wed May 22, 2019 6:12 am

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.

#4 Post by **asqwerth** » Wed May 22, 2019 6:15 am

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.

#5 Post by **sunrat** » Wed May 22, 2019 6:21 am

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

MX Linux Forum

Critical bug in 5.1 kernel?

Critical bug in 5.1 kernel?

Re: Critical bug in 5.1 kernel?

Re: Critical bug in 5.1 kernel?

Re: Critical bug in 5.1 kernel?

Re: Critical bug in 5.1 kernel?