@davidrevoy looking at the Git history, this might be the culprit: https://github.com/torvalds/linux/commit/276e14e6c3993317257e1787e93b7166fbc30905
@standingpad Thank you, that's also where my conclusion (the link in the last paragraph) is redirected.
Unfortunately, letting the kernel dev knowing about this is really hard (no 'issues' on Github, and the doc for reporting is .... well https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html ). Doing a blog post was my best option.
@davidrevoy @standingpad So normally you would report this to your distribution (Fedora) since this is a distro kernel -- upstream maintainers don't really know what patches are in your fedora kernel and can't take responsibility for it.
That said, it looks like the linked commit is a fix that probably isn't in your newer kernel, so there's some hope an even newer Fedora kernel will "magically" have the fix in a little while.
@vegard @standingpad Thank you for the information.
Ping @efi ; do you think it is still safe to send the issue to the kernel mailing list? I don't want to do any "faux pas" 🙂
@davidrevoy @vegard @standingpad maybe not, send it directly to the maintainer as a regular mail
@efi @vegard @standingpad Email sent to four maintainer and reviewer involved, and Jiri Kosina just replied adding CC to 9 other people involved and mailing-list. 🎉
Thanks for the recommandation. I think the info is in the right pipes now.