From: syzbot <syzbot+aea82bf9ee6ffd9a79d9@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dvyukov@google.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
rpenyaev@suse.de, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: WARNING in ep_poll_callback
Date: Mon, 07 Jan 2019 22:21:03 -0800 [thread overview]
Message-ID: <0000000000009546de057eec59be@google.com> (raw)
In-Reply-To: <000000000000d8bec0057eec0a92@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 139287cc2cc0 Add linux-next specific files for 20190108
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14c9dd4b400000
kernel config: https://syzkaller.appspot.com/x/.config?x=1521b074ff5a5bdf
dashboard link: https://syzkaller.appspot.com/bug?extid=aea82bf9ee6ffd9a79d9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1776034b400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c2e580c00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+aea82bf9ee6ffd9a79d9@syzkaller.appspotmail.com
------------[ cut here ]------------
IRQs not disabled as expected
WARNING: CPU: 0 PID: 7862 at fs/eventpoll.c:1224
ep_poll_callback+0x77e/0x1450 fs/eventpoll.c:1224
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 7862 Comm: syz-executor245 Not tainted 5.0.0-rc1-next-20190108
#7
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1db/0x2d0 lib/dump_stack.c:113
panic+0x2cb/0x65c kernel/panic.c:214
__warn.cold+0x20/0x48 kernel/panic.c:571
report_bug+0x263/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:271
do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:290
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:973
RIP: 0010:ep_poll_callback+0x77e/0x1450 fs/eventpoll.c:1224
Code: ff 44 89 ee e8 63 84 98 ff 45 84 ed 0f 85 4a fa ff ff e8 15 83 98 ff
48 c7 c7 00 69 56 88 c6 05 a1 b2 6e 08 01 e8 52 c8 61 ff <0f> 0b e9 2b fa
ff ff e8 f6 82 98 ff 48 8d 7b 30 48 b8 00 00 00 00
RSP: 0018:ffff8880924ff6a0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff88809241f480 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff816869f6 RDI: 0000000000000005
RBP: ffff8880924ff880 R08: ffff888099776640 R09: ffff888099776f30
R10: ffff888099776640 R11: 0000000000000000 R12: ffff8880924ff858
R13: 0000000000000000 R14: ffff88809241f4d0 R15: 0000000000000000
__wake_up_common+0x1d3/0x7d0 kernel/sched/wait.c:92
__wake_up_locked+0x11/0x20 kernel/sched/wait.c:154
fuse_abort_conn+0xd01/0x1200 fs/fuse/dev.c:2212
fuse_sb_destroy+0xd3/0x1d0 fs/fuse/inode.c:1245
fuse_kill_sb_anon+0x16/0x30 fs/fuse/inode.c:1256
deactivate_locked_super+0x9a/0x100 fs/super.c:331
deactivate_super fs/super.c:362 [inline]
deactivate_super+0x2ab/0x320 fs/super.c:358
cleanup_mnt+0xbf/0x160 fs/namespace.c:1140
__cleanup_mnt+0x16/0x20 fs/namespace.c:1147
task_work_run+0x1f4/0x2b0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:188 [inline]
exit_to_usermode_loop+0x32a/0x3b0 arch/x86/entry/common.c:166
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x696/0x800 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x440229
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 fb 13 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fffbe5bdb08 EFLAGS: 00000217 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00000000004002c8 RCX: 0000000000440229
RDX: 0000000000440229 RSI: 0000000000000000 RDI: 0000000020000040
RBP: 00000000006ca018 R08: 00000000004002c8 R09: 00000000004002c8
R10: 00000000004002c8 R11: 0000000000000217 R12: 0000000000401ab0
R13: 0000000000401b40 R14: 0000000000000000 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..
next prev parent reply other threads:[~2019-01-08 6:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 5:59 WARNING in ep_poll_callback syzbot
2019-01-08 6:00 ` Dmitry Vyukov
2019-01-08 10:05 ` Roman Penyaev
2019-01-08 6:21 ` syzbot [this message]
2019-03-11 13:14 ` syzbot
2019-03-11 13:37 ` Roman Penyaev
2019-03-11 13:45 ` Dmitry Vyukov
2019-03-11 13:53 ` Roman Penyaev
2019-03-11 16:36 ` Dmitry Vyukov
2019-03-11 16:36 ` syzbot
2019-03-11 16:37 ` Dmitry Vyukov
2019-03-11 17:22 ` Roman Penyaev
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=0000000000009546de057eec59be@google.com \
--to=syzbot+aea82bf9ee6ffd9a79d9@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpenyaev@suse.de \
--cc=sfr@canb.auug.org.au \
--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).