On Fri, May 29, 2020 at 6:57 PM Roger Heflin <rogerheflin(a)gmail.com> wrote:
I don't believe the
kernel.org developers work out of the fedora
bugzilla (or any distro's bugzilla), so no one who knows anything is
likely to find and/or see the bug.
To get a kernel developer you would need to at least post a summary to
the kernel subsystem list if you know which subsystem or the main
kernel if you don't.
And the
kernel.org guys do not care about any testing done on a fedora
delivered kernel as they don't know what code is in it, so you would
need to install a
kernel.org kernel and bot from it and verify you
have the issue on the newest released one.
I wish people read the thread or even posts carefully before
responding. I'm well aware that kernel developers are not watching
the Redhat BZ, but the maintainers are.
Anyway, here's an example of a healthy exchange on BZ:
- I reported this bug on Tuesday:
https://bugzilla.redhat.com/show_bug.cgi?id=1840432
- There was some discussion
- Today it got marked as a duplicate of this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1840780
- The maintainer had commented on the second bug on Wednesday that he
is too busy, and unlikely to find time to investigate
- On Thursday another person dug through the upstream repo, found the
commit that fixes the issue, determined that simply updating to the
latest version from upstream would fix the crash, and as a bonus
pointed to the underlying reason that caused the crash.
- Earlier today the maintainer did a scratch build of the latest
release, and asked for testing
- I happened to be online, after testing I responded that the build works
- Quite likely there will be a new release next week that pushes out the update.
--
Suvayu
Open source is the future. It sets us free.