From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+2778a29e60b4982065a0@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, Ming Lei <ming.lei@redhat.com>
Subject: Re: [syzbot] BUG: scheduling while atomic in simple_recursive_removal
Date: Thu, 31 Mar 2022 20:43:11 +0000 [thread overview]
Message-ID: <YkYSX0tibIE5o0h8@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <0000000000007564ac05db72ff58@google.com>
On Wed, Mar 30, 2022 at 10:37:22AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: d888c83fcec7 fs: fix fd table size alignment properly
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=103e7b53700000
> kernel config: https://syzkaller.appspot.com/x/.config?x=cadd7063134e07bc
> dashboard link: https://syzkaller.appspot.com/bug?extid=2778a29e60b4982065a0
> compiler: aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> userspace arch: arm64
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+2778a29e60b4982065a0@syzkaller.appspotmail.com
Very likely to have been caused by commit 0a9a25ca7843 "block: let blkcg_gq
grab request queue's refcnt".
It had added dropping a queue refcount (which is blocking) into blkg_free(),
which is called from __blkg_release(). And that is called via call_rcu()
and thus is not allowed to block at all.
next prev parent reply other threads:[~2022-03-31 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 17:37 [syzbot] BUG: scheduling while atomic in simple_recursive_removal syzbot
2022-03-31 20:43 ` Al Viro [this message]
2022-04-05 12:07 ` Bruno Goncalves
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=YkYSX0tibIE5o0h8@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=syzbot+2778a29e60b4982065a0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).