WARNING in fuse_dev_release

11 views
Skip to first unread message

syzbot

unread,
Dec 17, 2017, 11:38:05 AM12/17/17
to linux-...@vger.kernel.org, linux-...@vger.kernel.org, mik...@szeredi.hu, syzkall...@googlegroups.com
Hello,

syzkaller hit the following crash on
41d8c16909ebda40f7b4982a7f5e2ad102705ade
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Unfortunately, I don't have any reproducer for this bug yet.


WARNING: CPU: 1 PID: 4547 at fs/fuse/dev.c:2149 fuse_dev_release+0x84/0xa0
fs/fuse/dev.c:2149
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 4547 Comm: syz-executor2 Not tainted 4.15.0-rc3-next-20171213+
#66
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xe9/0x14b lib/dump_stack.c:53
panic+0x10e/0x2f8 kernel/panic.c:183
__warn+0x14e/0x150 kernel/panic.c:547
report_bug+0x11e/0x1a0 lib/bug.c:184
fixup_bug.part.11+0x17/0x30 arch/x86/kernel/traps.c:177
fixup_bug arch/x86/kernel/traps.c:246 [inline]
do_error_trap+0x14a/0x180 arch/x86/kernel/traps.c:295
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:314
invalid_op+0x22/0x40 arch/x86/entry/entry_64.S:1079
RIP: 0010:fuse_dev_release+0x84/0xa0 fs/fuse/dev.c:2149
RSP: 0018:ffffc900013a7be8 EFLAGS: 00010293
RAX: ffff8801e34c4480 RBX: ffff8801e4aa0500 RCX: ffffffff815f43d4
RDX: 0000000000000000 RSI: ffff8801e4cabc00 RDI: ffff8802160106b0
RBP: ffffc900013a7bf8 R08: 0000000000000000 R09: 0000000000000004
R10: ffffc900013a7bf8 R11: 0000000000000000 R12: ffff8801e37ca810
R13: ffff8801e4cabc00 R14: ffff8802160106b0 R15: ffff8802160106b0
cuse_channel_release+0xcd/0xe0 fs/fuse/cuse.c:555
__fput+0x120/0x270 fs/file_table.c:209
____fput+0x15/0x20 fs/file_table.c:243
task_work_run+0xa3/0xe0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x3e6/0x1050 kernel/exit.c:869
do_group_exit+0x60/0x100 kernel/exit.c:972
get_signal+0x36c/0xad0 kernel/signal.c:2337
do_signal+0x23/0x670 arch/x86/kernel/signal.c:809
exit_to_usermode_loop+0x13c/0x160 arch/x86/entry/common.c:161
prepare_exit_to_usermode arch/x86/entry/common.c:195 [inline]
syscall_return_slowpath+0x1b4/0x1e0 arch/x86/entry/common.c:264
entry_SYSCALL_64_fastpath+0x94/0x96
RIP: 0033:0x452a39
RSP: 002b:00007ffbc43e4ce8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000000 RBX: 0000000000758048 RCX: 0000000000452a39
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000758048
RBP: 0000000000758048 R08: 000000000000019a R09: 0000000000758020
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000a6f7ff R14: 00007ffbc43e59c0 R15: 0000000000000000
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
config.txt
raw.log

Dmitry Vyukov

unread,
Feb 14, 2018, 9:52:51 AM2/14/18
to syzbot, syzkall...@googlegroups.com
old bug bankruptcy

#syz invalid

On Sun, Dec 17, 2017 at 5:38 PM, syzbot
<bot+d75850dba219614392...@syzkaller.appspotmail.com>
wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/001a1144d1c86cbacb05608bdbd1%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages