From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+31e8daa8b3fc129e75f2@syzkaller.appspotmail.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
Omar Sandoval <osandov@osandov.com>
Subject: Re: WARNING: lock held when returning to user space!
Date: Fri, 6 Apr 2018 08:27:06 -0600 [thread overview]
Message-ID: <0e998b77-14f0-aee0-8d32-bc1dd96fcc4c@kernel.dk> (raw)
In-Reply-To: <00000000000082922905692da9e1@google.com>
On 4/6/18 7:02 AM, syzbot wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +0000)
> Merge tag 'armsoc-drivers' of
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
> syzbot dashboard link:
> https://syzkaller.appspot.com/bug?extid=31e8daa8b3fc129e75f2
>
> So far this crash happened 9 times on upstream.
> C reproducer: https://syzkaller.appspot.com/x/repro.c?id=6407930337296384
> syzkaller reproducer:
> https://syzkaller.appspot.com/x/repro.syz?id=4942413340606464
> Raw console output:
> https://syzkaller.appspot.com/x/log.txt?id=4764483918495744
> Kernel config:
> https://syzkaller.appspot.com/x/.config?id=-5813481738265533882
> compiler: gcc (GCC) 8.0.1 20180301 (experimental)
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+31e8daa8b3fc129e75f2@syzkaller.appspotmail.com
> It will help syzbot understand when the bug is fixed. See footer for
> details.
> If you forward the report, please keep this part and the footer.
>
>
> ================================================
> WARNING: lock held when returning to user space!
> 4.16.0+ #3 Not tainted
> ------------------------------------------------
> syzkaller433111/4462 is leaving the kernel with locks still held!
> 1 lock held by syzkaller433111/4462:
> #0: 0000000003a06fae (&lo->lo_ctl_mutex/1){+.+.}, at: lo_ioctl+0x8d/0x1ec0
> drivers/block/loop.c:1363
Is this a new regression? Omar did just fiddle with the locking a bit,
seems suspicious.
--
Jens Axboe
next prev parent reply other threads:[~2018-04-06 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 13:02 WARNING: lock held when returning to user space! syzbot
2018-04-06 14:27 ` Jens Axboe [this message]
2018-04-06 14:57 ` Dmitry Vyukov
2018-04-06 15:01 ` Jens Axboe
2018-04-14 15:33 ` Tetsuo Handa
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=0e998b77-14f0-aee0-8d32-bc1dd96fcc4c@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=syzbot+31e8daa8b3fc129e75f2@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