From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Eric Dumazet <edumazet@google.com>,
syzbot <syzbot+51cd74c5dfeafd65e488@syzkaller.appspotmail.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
davem@davemloft.net, dsahern@kernel.org, hdanton@sina.com,
horms@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [net?] [mm?] INFO: rcu detected stall in inet_rtm_newaddr (2)
Date: Tue, 14 Oct 2025 23:11:49 +0300 [thread overview]
Message-ID: <20251014201149.ckkw7okat3cv55qk@skbuf> (raw)
In-Reply-To: <CAM0EoMmK7TJ4w_heeMuD+YmUdMyEz7VWKY+a+qMO2UN4GYZ5jQ@mail.gmail.com>
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.
What is the situation with syzbot reports? I don't actively monitor them,
only if somebody happens to email me.
next prev parent reply other threads:[~2025-10-14 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <681a1770.050a0220.a19a9.000d.GAE@google.com>
2025-10-11 7:41 ` syzbot
2025-10-11 9:42 ` Eric Dumazet
2025-10-12 15:46 ` Jamal Hadi Salim
2025-10-12 15:52 ` Jamal Hadi Salim
2025-10-14 20:11 ` Vladimir Oltean [this message]
2025-10-15 21:50 ` Jamal Hadi Salim
2025-10-13 21:51 ` Vinicius Costa Gomes
2025-10-15 21:36 ` Jamal Hadi Salim
2025-10-15 22:30 ` Vinicius Costa Gomes
2025-10-24 0:11 ` Vinicius Costa Gomes
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=20251014201149.ckkw7okat3cv55qk@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+51cd74c5dfeafd65e488@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vinicius.gomes@intel.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