From: syzbot <syzbot+9331a354f4f624a52a55@syzkaller.appspotmail.com>
To: jiufei.xue@linux.alibaba.com, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
mszeredi@redhat.com, syzkaller-bugs@googlegroups.com
Subject: WARNING: lock held when returning to user space in ovl_write_iter
Date: Sun, 01 Mar 2020 11:13:14 -0800 [thread overview]
Message-ID: <000000000000cc1faf059fcfdc73@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: bdc5461b Add linux-next specific files for 20200224
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10deee65e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8402e437f1eeea92
dashboard link: https://syzkaller.appspot.com/bug?extid=9331a354f4f624a52a55
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1571d22de00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175192c3e00000
The bug was bisected to:
commit 2406a307ac7ddfd7effeeaff6947149ec6a95b4e
Author: Jiufei Xue <jiufei.xue@linux.alibaba.com>
Date: Wed Nov 20 09:45:26 2019 +0000
ovl: implement async IO routines
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113c6d29e00000
final crash: https://syzkaller.appspot.com/x/report.txt?x=133c6d29e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=153c6d29e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+9331a354f4f624a52a55@syzkaller.appspotmail.com
Fixes: 2406a307ac7d ("ovl: implement async IO routines")
================================================
WARNING: lock held when returning to user space!
5.6.0-rc2-next-20200224-syzkaller #0 Not tainted
------------------------------------------------
syz-executor184/10029 is leaving the kernel with locks still held!
1 lock held by syz-executor184/10029:
#0: ffff88809987c418 (sb_writers#3){.+.+}, at: file_start_write include/linux/fs.h:2903 [inline]
#0: ffff88809987c418 (sb_writers#3){.+.+}, at: ovl_write_iter+0xcc1/0x1090 fs/overlayfs/file.c:348
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2020-03-01 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 19:13 syzbot [this message]
2020-03-12 15:30 ` WARNING: lock held when returning to user space in ovl_write_iter Miklos Szeredi
2020-03-12 18:35 ` syzbot
2020-03-13 8:53 ` Miklos Szeredi
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=000000000000cc1faf059fcfdc73@google.com \
--to=syzbot+9331a354f4f624a52a55@syzkaller.appspotmail.com \
--cc=jiufei.xue@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.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 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.