linux-kernel - Re: [syzbot] [net?] [mm?] INFO: rcu detected stall in inet_rtm

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: <CAM0EoM=1swUNW5F2Ha4JCf3VW309m1S0JEpSqiyR5wH7e=YyJw@mail.gmail.com>
Date: Wed, 15 Oct 2025 17:50:41 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: Eric Dumazet <edumazet@...gle.com>, 
	syzbot <syzbot+51cd74c5dfeafd65e488@...kaller.appspotmail.com>, 
	Vinicius Costa Gomes <vinicius.gomes@...el.com>, davem@...emloft.net, dsahern@...nel.org, 
	hdanton@...a.com, horms@...nel.org, kuba@...nel.org, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, netdev@...r.kernel.org, 
	pabeni@...hat.com, syzkaller-bugs@...glegroups.com, tglx@...utronix.de
Subject: Re: [syzbot] [net?] [mm?] INFO: rcu detected stall in
 inet_rtm_newaddr (2)

On Tue, Oct 14, 2025 at 4:11 PM Vladimir Oltean <vladimir.oltean@....com> wrote:
>
> Hi Jamal,
>
> On Sun, Oct 12, 2025 at 11:52:54AM -0400, Jamal Hadi Salim wrote:
> > > > Yet another taprio report.
> > > >
> > > > If taprio can not be fixed, perhaps we should remove it from the
> > > > kernel, or clearly marked as broken.
> > > > (Then ask syzbot to no longer include it)
> > >
> > > Agreed on the challenge with taprio.
> > > We need the stakeholders input: Vinicius - are you still working in
> > > this space? Vladimir you also seem to have interest (or maybe nxp
> > > does) in this?
> >
> > + Vladmir..
> >
> > > At a minimum, we should mark it as broken unless the stakeholders want
> > > to actively fix these issues.
> > > Would syzbot still look at it if it was marked broken?
>
> I still have interest in taprio, but at the moment I can't look at this
> any sooner than the second half of next week (unless someone else beats
> me to it). I've added a note not to lose track.
>

Thanks!

> What is the situation with syzbot reports? I don't actively monitor them,
> only if somebody happens to email me.

These issues have been lingering forever..
They do get posted on the list. Here are samples:
https://lore.kernel.org/netdev/676d25b2.050a0220.2f3838.0464.GAE@google.com/#r
https://lore.kernel.org/netdev/67d2a576.050a0220.14e108.0030.GAE@google.com/
https://lore.kernel.org/netdev/67946a0c.050a0220.3ab881.0010.GAE@google.com/
https://lore.kernel.org/netdev/66e96979.050a0220.252d9a.000a.GAE@google.com/
https://lore.kernel.org/netdev/6777334a.050a0220.3a8527.0058.GAE@google.com/#t

They all point to the same bisected commit, but am not sure whether
they are the same issue

To get you on Cc from syzbot - i think we'll have to add you as a
maintainer for taprio if you'd be okk with that..

cheers,
jamal