From: Jakub Kicinski <kuba@kernel.org>
To: Bonus <kernel@bonusplay.pl>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
netdev@vger.kernel.org
Subject: Re: be2net: oops due to RCU context switch
Date: Tue, 14 Jan 2025 11:08:49 -0800 [thread overview]
Message-ID: <20250114110849.0eb0ff2c@kernel.org> (raw)
In-Reply-To: <515516c7-e6e9-450a-9a74-685a60d64497@bonusplay.pl>
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.
next prev parent reply other threads:[~2025-01-14 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 10:37 be2net: oops due to RCU context switch Bonus
2025-01-14 10:49 ` Bonus
2025-01-14 19:08 ` Jakub Kicinski [this message]
2025-01-14 22:09 ` Bonus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250114110849.0eb0ff2c@kernel.org \
--to=kuba@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=kernel@bonusplay.pl \
--cc=netdev@vger.kernel.org \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).