From: Nikolay Ivchenko <nivchenko.dev@gmail.com>
To: hdanton@sina.com
Cc: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
jhs@mojatatu.com, jiri@resnulli.us, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com,
syzbot+2ad5ec205a38c46522b3@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, vinicius.gomes@intel.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in unmap_region
Date: Fri, 24 Jul 2026 23:27:53 +0300 [thread overview]
Message-ID: <20260724202753.248227-1-nivchenko.dev@gmail.com> (raw)
In-Reply-To: <20260722125604.664-1-hdanton@sina.com>
> A known issue, feel free to grep broken in the 2025 report [1].
>
> [1] Subject: Re: [syzbot] [net?] [mm?] INFO: rcu detected stall in inet_rtm_newaddr (2)
> https://lore.kernel.org/lkml/CANn89iLjjtXV3ZMxfQDb1bbsVJ6a_Chexu4FwqeejxGTwsR_kg@mail.gmail.com/
Thanks for the link, Hillf. I read through that thread and also looked at
several other open syzbot reports with "stall" in the subject line that have
replies from other developers:
- https://syzkaller.appspot.com/bug?extid=385468161961cee80c31
- https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa
- https://syzkaller.appspot.com/bug?extid=c28b5fee66fd3b7f766e
- https://syzkaller.appspot.com/bug?extid=9f78d5c664a8c33f4cce
- https://syzkaller.appspot.com/bug?extid=69904c3b4a09e8fa2e1b
- https://syzkaller.appspot.com/bug?extid=51cd74c5dfeafd65e488
- https://syzkaller.appspot.com/bug?extid=5b4f4f81240931b16844
- https://syzkaller.appspot.com/bug?extid=4507914ec56d21bb39ed
- https://syzkaller.appspot.com/bug?extid=0635dc2e2c3c21a6aa04
In the reports similar to this one, all the attached reproducers configure
taprio with very small timer intervals. I haven't gone through all the
comments and proposed patches in those other reports yet, but I'm looking
into them now.
> How many hours were spent?
>
> And my 2cents suggestion sounds like sit back with netflix on.
I would gladly do that, but it really bothers me that there's a single
issue generating a flood of different bug reports on syzbot. As you
rightly pointed out - how many hours have already been spent investigating
them, and how many more will be wasted?
From what I can tell so far, this remains unfixed simply because no one
has fixed it yet, correct? Please correct me if I'm wrong and missed
other discussions on this topic. If that's the case, I'll try to propose
some solutions for this issue.
Best regards,
Nikolay Ivchenko
prev parent reply other threads:[~2026-07-24 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 7:03 [syzbot] [mm?] INFO: rcu detected stall in unmap_region syzbot
2026-07-22 7:14 ` Nikolay Ivchenko
2026-07-22 12:56 ` Hillf Danton
2026-07-24 20:27 ` Nikolay Ivchenko [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=20260724202753.248227-1-nivchenko.dev@gmail.com \
--to=nivchenko.dev@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+2ad5ec205a38c46522b3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.