mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Mingcong Bai <jeffbai@aosc.io>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>, rcu <rcu@vger.kernel.org>,
	sakiiily@aosc.io, Kexy Biscuit <kexybiscuit@aosc.io>
Subject: Re: [Regression] wifi problems since tg3 started throwing rcu stall warnings
Date: Tue, 19 Nov 2024 11:43:59 +0100	[thread overview]
Message-ID: <Zzxr72hkv8DAwjMG@pavilion.home> (raw)
In-Reply-To: <720576d090304a33b7d9ba3348056717@aosc.io>

Le Fri, Nov 15, 2024 at 11:01:25AM +0800, Mingcong Bai a écrit :
> Hi Frederic,
> 
> <snip>
> 
> > Just in case, Mingcong Bai can you test the following patch without the
> > revert and see if it triggers something?
> > 
> > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> > index 35949ec1f935..b4f8ed8138d3 100644
> > --- a/kernel/rcu/tree.c
> > +++ b/kernel/rcu/tree.c
> > @@ -5170,6 +5170,7 @@ void rcutree_migrate_callbacks(int cpu)
> >  	struct rcu_data *rdp = per_cpu_ptr(&rcu_data, cpu);
> >  	bool needwake;
> > 
> > +	WARN_ON_ONCE(1);
> >  	if (rcu_rdp_is_offloaded(rdp))
> >  		return;
> > 
> 
> Please find attached the dmesg with your patch (and no revert) against
> 6.12-rc7.

The added WARN_ON_ONCE() doesn't trigger so the function/path changed by this patch
isn't taken.

My only guess is that the patch changes some code layout that makes a bug more
likely to appear in networking...

Thanks.

> 
> Best Regards,
> Mingcong Bai
> 
> > 
> > 
> > Thanks.
> > 
> > > 
> > > 							Thanx, Paul



      reply	other threads:[~2024-11-19 10:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  8:27 Linux regression tracking (Thorsten Leemhuis)
2024-10-23  9:11 ` Linux regression tracking (Thorsten Leemhuis)
2024-10-23 10:09 ` Frederic Weisbecker
2024-10-23 10:22   ` Linux regression tracking (Thorsten Leemhuis)
2024-11-05  7:17     ` Mingcong Bai
2024-11-07  9:10       ` Thorsten Leemhuis
2024-11-07 10:04         ` Frederic Weisbecker
2024-11-07 10:33           ` Mingcong Bai
2024-11-07 16:29           ` Mingcong Bai
2024-11-08 13:46             ` Frederic Weisbecker
2024-11-08 15:14               ` Paul E. McKenney
2024-11-12 12:50                 ` Frederic Weisbecker
2024-11-15  3:01                   ` Mingcong Bai
2024-11-19 10:43                     ` Frederic Weisbecker [this message]

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=Zzxr72hkv8DAwjMG@pavilion.home \
    --to=frederic@kernel.org \
    --cc=jeffbai@aosc.io \
    --cc=kexybiscuit@aosc.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sakiiily@aosc.io \
    /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

all inboxes | Powered by JetHome®