From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+cdcbdc0bd42e559b52b9@syzkaller.appspotmail.com>,
io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: inconsistent lock state in xa_destroy
Date: Thu, 8 Oct 2020 09:01:57 -0600 [thread overview]
Message-ID: <de842e7f-fa50-193b-b1d7-c573e515ef8b@kernel.dk> (raw)
In-Reply-To: <00000000000045ac4605b12a1720@google.com>
On 10/8/20 9:00 AM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: e4fb79c7 Add linux-next specific files for 20201008
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12555227900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=568d41fe4341ed0f
> dashboard link: https://syzkaller.appspot.com/bug?extid=cdcbdc0bd42e559b52b9
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> 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+cdcbdc0bd42e559b52b9@syzkaller.appspotmail.com
Already pushed out a fix for this, it's really an xarray issue where it just
assumes that destroy can irq grab the lock.
#syz fix: io_uring: no need to call xa_destroy() on empty xarray
--
Jens Axboe
next prev parent reply other threads:[~2020-10-08 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 15:00 inconsistent lock state in xa_destroy syzbot
2020-10-08 15:01 ` Jens Axboe [this message]
2020-10-08 15:05 ` Matthew Wilcox
2020-10-08 15:06 ` Jens Axboe
2020-10-08 15:28 ` Matthew Wilcox
2020-10-08 15:32 ` Jens Axboe
2020-10-08 21:14 ` syzbot
2020-10-08 22:27 ` Matthew Wilcox
2020-10-09 0:55 ` Jens Axboe
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=de842e7f-fa50-193b-b1d7-c573e515ef8b@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+cdcbdc0bd42e559b52b9@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).