netdev - Re: [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153 Gigabit Ethernet Adapter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9284a9ec-d7c9-68e8-7384-07291894937b@leemhuis.info>
Date: Sat, 6 May 2023 08:20:23 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Linux regressions mailing list <regressions@...ts.linux.dev>,
 Bjørn Mork <bjorn@...k.no>,
 Hayes Wang <hayeswang@...ltek.com>, netdev@...r.kernel.org,
 Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>,
 "David S. Miller" <davem@...emloft.net>, Stanislav Fomichev <sdf@...ichev.me>
Subject: Re: [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153
 Gigabit Ethernet Adapter

On 05.05.23 21:37, Jakub Kicinski wrote:
> On Fri, 5 May 2023 21:20:15 +0200 Linux regression tracking (Thorsten
> Leemhuis) wrote:
>>> Thorsten, how is the communication supposed to work in this case?
>>> Can you ask the reporter to test this?  
>>
>> I'd prefer to not become the man-in-the middle, that just delays things
>> and is fragile; but I can do that occasionally if developers really are
>> unwilling to go to bugzilla.
>>
>> Bugbot afaics will solve this, but using it right now would require me
>> to do something some maintainers don't like. See this sub-thread:
>>
>> https://lore.kernel.org/all/1f0ebf13-ab0f-d512-6106-3ebf7cb372f1@leemhuis.info/
>>
>> :-/
>>
>> This got me thinking: we could tell bugbot to start monitoring this
>> thread and then tell the reporter to CC to the new bug bugbot created.
>> Ugly, but might work.
>>
>>> I don't see them on CC...  
>>
>> Yeah, as stated in the initial mail of this thread: I sadly can't CC
>> them, because bugzilla.kernel.org tells users upon registration their
>> "email address will never be displayed to logged out users"... #sigh
>>
>> I wish things were different, I'm unhappy about this situation myself.
> 
> Let's work something out, because forwarding enough info for Bjorn to
> respond on the list means that we now have the conversation going in
> both places. So it's confusing & double the work for developers.

I know, I know, but I saw no other way.

> I don't seem to have the permissions on BZ, but I'm guessing we could
> do the opposite - you could flip bugbot on first to have it flush the BZ
> report to the list, and then reply on the list with regzbot tracking?

That's the plan for the future, but for now I don't want to do that, as
it might mess up other peoples workflows, as hinted above already and
discussed here:

https://lore.kernel.org/all/1f0ebf13-ab0f-d512-6106-3ebf7cb372f1@leemhuis.info/

That was only recently, but if you jump in there as well it might
persuade Konstantin to enable bugbot for other products/components. Then
I could and would do what you suggested.

Ciao, Thorsten