On 12/3/18 8:46 AM, Reindl Harald wrote:
Am 03.12.18 um 17:42 schrieb Laura Abbott:
On 12/2/18 6:20 AM, Reindl Harald wrote:
how does Fedora think to handle
https://bugzilla.kernel.org/show_bug.cgi?id=201685
4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs
fine on F28 systems but given that bug upgrade to 4.19.x seems to be
just a lottery with your data - on some or even many systems all seems
to be fine BUT when you are affected and nobody until now knows the root
cause
honestly the rebase to 4.19 was too fast to start with!
WHY did that rebase happen at all?
kernel-4.19.2-200.fc28 jcline 2018-11-15 01:34:18
bug reported: 2018-11-13 19:42:20 UTC
and yes i had that bugreport in my inbox just because i have subscribed
to filesystem / raid related mailing lists and the word "crazy" appeared
in my mind when i saw the rebase two days later because i expect that
downstream maintainers at least have the same lists subscribed ordinary
users have
We're working with the upstream maintainers to narrow down the problem.
At least on Fedora we haven't seen any reports of corruption reported
on our bugzilla which is a useful data point for the upstream maintainers.
We'll keep you updated if we find anything.
here you have the first Fedora user upstream
https://bugzilla.kernel.org/show_bug.cgi?id=201685#c198
There's now a fix proposed upstream
https://bugzilla.kernel.org/show_bug.cgi?id=201685#c255
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
