From: Ming Lei <ming.lei@redhat.com>
To: syzbot <syzbot+3ba0493d523d007b3819@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, cgroups@vger.kernel.org, fweisbec@gmail.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tj@kernel.org
Subject: Re: [syzbot] INFO: rcu detected stall in net_tx_action
Date: Thu, 28 Jul 2022 00:00:07 +0800 [thread overview]
Message-ID: <YuFhB2FaEacNI26/@T590> (raw)
In-Reply-To: <0000000000004bee3605e4b74106@google.com>
On Tue, Jul 26, 2022 at 08:50:09AM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 0a9a25ca78437b39e691bcc3dc8240455b803d8d
> Author: Ming Lei <ming.lei@redhat.com>
> Date: Fri Mar 18 13:01:43 2022 +0000
>
> block: let blkcg_gq grab request queue's refcnt
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1004f05a080000
> start commit: d6765985a42a Revert "be2net: disable bh with spin_lock in ..
> git tree: net
> kernel config: https://syzkaller.appspot.com/x/.config?x=7ca96a2d153c74b0
> dashboard link: https://syzkaller.appspot.com/bug?extid=3ba0493d523d007b3819
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c9edc8300000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=172463c8300000
>
The bad commit has been fixed by the following patch:
d578c770c852 block: avoid calling blkg_free() in atomic context
Thanks,
Ming
prev parent reply other threads:[~2022-07-27 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 15:50 [syzbot] INFO: rcu detected stall in net_tx_action syzbot
2022-07-26 15:50 ` syzbot
2022-07-27 16:00 ` Ming Lei [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=YuFhB2FaEacNI26/@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=fweisbec@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+3ba0493d523d007b3819@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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).