All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3ba0493d523d007b3819@syzkaller.appspotmail.com>
To: axboe@kernel.dk, cgroups@vger.kernel.org, fweisbec@gmail.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	ming.lei@redhat.com, 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: Tue, 26 Jul 2022 08:50:09 -0700	[thread overview]
Message-ID: <0000000000004bee3605e4b74106@google.com> (raw)
In-Reply-To: <00000000000026864605c611cc51@google.com>

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

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: block: let blkcg_gq grab request queue's refcnt

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2022-07-26 15:50 UTC|newest]

Thread overview: 17+ 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 [this message]
2022-07-27 16:00   ` Ming Lei
     [not found] <20220727120100.2928-1-hdanton@sina.com>
2022-07-27 12:14 ` syzbot
     [not found] <20220727130039.287-1-hdanton@sina.com>
2022-07-27 13:16 ` syzbot
     [not found] <20220727132847.227-1-hdanton@sina.com>
2022-07-27 13:44 ` syzbot
     [not found] <20220728001258.311-1-hdanton@sina.com>
2022-07-28  0:27 ` syzbot
     [not found] <20220728024623.492-1-hdanton@sina.com>
2022-07-28  2:59 ` syzbot
     [not found] <20220728032630.611-1-hdanton@sina.com>
2022-07-28  3:44 ` syzbot
     [not found] <20220728042901.668-1-hdanton@sina.com>
2022-07-28  4:49 ` syzbot
     [not found] <20220728073322.731-1-hdanton@sina.com>
2022-07-28  7:46 ` syzbot
     [not found] <20220728081331.805-1-hdanton@sina.com>
2022-07-28  8:34 ` syzbot
     [not found] <20220728095628.903-1-hdanton@sina.com>
2022-07-28 10:16 ` syzbot
     [not found] <20220730094728.1144-1-hdanton@sina.com>
2022-07-30 11:16 ` syzbot
     [not found] <20220730114424.1197-1-hdanton@sina.com>
2022-07-30 15:29 ` syzbot
     [not found] <20220730223316.1270-1-hdanton@sina.com>
2022-07-30 22:44 ` syzbot
     [not found] <20220731020212.1439-1-hdanton@sina.com>
2022-07-31  2:21 ` syzbot

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=0000000000004bee3605e4b74106@google.com \
    --to=syzbot+3ba0493d523d007b3819@syzkaller.appspotmail.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=ming.lei@redhat.com \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 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.