netdev - Re: be2net: oops due to RCU context switch

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] [day] [month] [year] [list]

Message-ID: <0f41d81b-8ba3-464f-b0d0-701b3bfc3694@bonusplay.pl>
Date: Tue, 14 Jan 2025 23:09:24 +0100
From: Bonus <kernel@...usplay.pl>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Ajit Khaparde <ajit.khaparde@...adcom.com>,
 Sriharsha Basavapatna <sriharsha.basavapatna@...adcom.com>,
 Somnath Kotur <somnath.kotur@...adcom.com>, netdev@...r.kernel.org
Subject: Re: be2net: oops due to RCU context switch

On 1/14/25 20:08, Jakub Kicinski wrote:
> On Tue, 14 Jan 2025 11:37:36 +0100 Bonus wrote:
>> I've encountered a regression with kernel 6.12 immediately after 
>> booting. I don't encounter it on 6.6. If required i can try to bisect 
>> it, as it is very easy to reproduce.
> Hm. Bisection would be helpful. I scrolled back 2 years, I don't see
> anything very relevant. The driver sees very few changes these days.
> ndo_bridge_getlink has always been called under RCU.

I probably should have done debugging on my side, before reporting this here.
Turns out, this is somehow NVIDIA's driver fault.
Blacklisting it and booting with nouveau fixes the problem.

Kind Regards,
Bonus