WARNING in __device_add_disk
21 views
Skip to first unread message
syzbot
Apr 19, 2018, 1:06:03 PM4/19/18
to ax...@kernel.dk, linux...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
Hello,
syzbot hit the following crash on upstream commit
87ef12027b9b1dd0e0b12cf311fbcb19f9d92539 (Wed Apr 18 19:48:17 2018 +0000)
Merge tag 'ceph-for-4.17-rc2' of git://github.com/ceph/ceph-client
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=3337db851ace689ceb50
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=5356500264419328
Kernel config:
https://syzkaller.appspot.com/x/.config?id=1808800213120130118
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+3337db...@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.
RAX: ffffffffffffffda RBX: 00007fee9fefc6d4 RCX: 0000000000455329
RDX: 0000000020000000 RSI: 0000000000004c80 RDI: 0000000000000014
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000015
R13: 00000000000002a2 R14: 00000000006f6fd0 R15: 0000000000000036
WARNING: CPU: 1 PID: 30128 at block/genhd.c:685
__device_add_disk+0x104a/0x1340 block/genhd.c:685
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 30128 Comm: syz-executor3 Not tainted 4.17.0-rc1+ #8
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+0x1b9/0x294 lib/dump_stack.c:113
panic+0x22f/0x4de kernel/panic.c:184
__warn.cold.8+0x163/0x1b3 kernel/panic.c:536
report_bug+0x252/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x1de/0x490 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:992
RIP: 0010:__device_add_disk+0x104a/0x1340 block/genhd.c:685
RSP: 0018:ffff8801b320f8a8 EFLAGS: 00010246
RAX: 0000000000040000 RBX: ffff8801d7fbe880 RCX: ffffc90007714000
RDX: 0000000000040000 RSI: ffffffff83434d6a RDI: 0000000000000005
RBP: ffff8801b320fa78 R08: ffff8801a9364400 R09: ffffed003b5e46c2
R10: ffffed003b5e46c2 R11: ffff8801daf23613 R12: 00000000fffffff4
R13: ffff8801b320fa50 R14: ffff8801d7fbede0 R15: ffff8801d7fbe884
device_add_disk+0x22/0x30 block/genhd.c:705
add_disk include/linux/genhd.h:397 [inline]
loop_add+0x70b/0x9c0 drivers/block/loop.c:1873
loop_control_ioctl+0x178/0x500 drivers/block/loop.c:1970
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x1cf/0x16a0 fs/ioctl.c:684
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:701
__do_sys_ioctl fs/ioctl.c:708 [inline]
__se_sys_ioctl fs/ioctl.c:706 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:706
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455329
RSP: 002b:00007fee9fefbc68 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fee9fefc6d4 RCX: 0000000000455329
RDX: 0000000020000000 RSI: 0000000000004c80 RDI: 0000000000000014
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000015
R13: 00000000000002a2 R14: 00000000006f6fd0 R15: 0000000000000036
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.
syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please 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.
syzbot hit the following crash on upstream commit
87ef12027b9b1dd0e0b12cf311fbcb19f9d92539 (Wed Apr 18 19:48:17 2018 +0000)
Merge tag 'ceph-for-4.17-rc2' of git://github.com/ceph/ceph-client
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=3337db851ace689ceb50
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=5356500264419328
Kernel config:
https://syzkaller.appspot.com/x/.config?id=1808800213120130118
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+3337db...@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.
RAX: ffffffffffffffda RBX: 00007fee9fefc6d4 RCX: 0000000000455329
RDX: 0000000020000000 RSI: 0000000000004c80 RDI: 0000000000000014
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000015
R13: 00000000000002a2 R14: 00000000006f6fd0 R15: 0000000000000036
WARNING: CPU: 1 PID: 30128 at block/genhd.c:685
__device_add_disk+0x104a/0x1340 block/genhd.c:685
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 30128 Comm: syz-executor3 Not tainted 4.17.0-rc1+ #8
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+0x1b9/0x294 lib/dump_stack.c:113
panic+0x22f/0x4de kernel/panic.c:184
__warn.cold.8+0x163/0x1b3 kernel/panic.c:536
report_bug+0x252/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x1de/0x490 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:992
RIP: 0010:__device_add_disk+0x104a/0x1340 block/genhd.c:685
RSP: 0018:ffff8801b320f8a8 EFLAGS: 00010246
RAX: 0000000000040000 RBX: ffff8801d7fbe880 RCX: ffffc90007714000
RDX: 0000000000040000 RSI: ffffffff83434d6a RDI: 0000000000000005
RBP: ffff8801b320fa78 R08: ffff8801a9364400 R09: ffffed003b5e46c2
R10: ffffed003b5e46c2 R11: ffff8801daf23613 R12: 00000000fffffff4
R13: ffff8801b320fa50 R14: ffff8801d7fbede0 R15: ffff8801d7fbe884
device_add_disk+0x22/0x30 block/genhd.c:705
add_disk include/linux/genhd.h:397 [inline]
loop_add+0x70b/0x9c0 drivers/block/loop.c:1873
loop_control_ioctl+0x178/0x500 drivers/block/loop.c:1970
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x1cf/0x16a0 fs/ioctl.c:684
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:701
__do_sys_ioctl fs/ioctl.c:708 [inline]
__se_sys_ioctl fs/ioctl.c:706 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:706
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455329
RSP: 002b:00007fee9fefbc68 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fee9fefc6d4 RCX: 0000000000455329
RDX: 0000000020000000 RSI: 0000000000004c80 RDI: 0000000000000014
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000015
R13: 00000000000002a2 R14: 00000000006f6fd0 R15: 0000000000000036
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.
syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please 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.
syzbot
Apr 30, 2018, 8:37:02 AM4/30/18
to ax...@kernel.dk, linux...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
syzbot has found reproducer for the following crash on upstream commit
6da6c0db5316275015e8cc2959f12a17584aeb64 (Sun Apr 29 21:17:42 2018 +0000)
Linux v4.17-rc3
So far this crash happened 2 times on upstream.
C reproducer: https://syzkaller.appspot.com/x/repro.c?id=5078600311111680
syzkaller reproducer:
https://syzkaller.appspot.com/x/repro.syz?id=5938566311968768
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=6326042692157440
Kernel config:
https://syzkaller.appspot.com/x/.config?id=6493557782959164711
RDX: 00000000004a1d2c RSI: 0000000020000080 RDI: 00000000200000c0
RBP: 0030656c69662f2e R08: 00007fffca04f610 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000401d90
R13: 0000000000401e20 R14: 0000000000000000 R15: 0000000000000000
WARNING: CPU: 1 PID: 4539 at block/genhd.c:685
RAX: ffff8801d908e380 RBX: ffff8801d95d8e80 RCX: ffffffff83437c33
RDX: 0000000000000000 RSI: ffffffff83437d6a RDI: 0000000000000005
RBP: ffff8801ad26f6b0 R08: ffff8801d908e380 R09: 0000000000000006
R10: ffff8801d908e380 R11: 0000000000000000 R12: 00000000fffffff4
R13: ffff8801ad26f688 R14: ffff8801d95d93e0 R15: ffff8801d95d8e84
loop_probe+0x185/0x1c0 drivers/block/loop.c:1967
kobj_lookup+0x269/0x460 drivers/base/map.c:124
get_gendisk+0x4c/0x380 block/genhd.c:813
bdev_get_gendisk fs/block_dev.c:1063 [inline]
bd_start_claiming fs/block_dev.c:1118 [inline]
blkdev_get+0x16a/0xb30 fs/block_dev.c:1604
blkdev_get_by_path+0x5c/0xe0 fs/block_dev.c:1689
mount_bdev+0x5d/0x3e0 fs/super.c:1122
fuse_mount_blk+0x34/0x40 fs/fuse/inode.c:1222
mount_fs+0xae/0x328 fs/super.c:1267
vfs_kern_mount.part.34+0xd4/0x4d0 fs/namespace.c:1037
vfs_kern_mount fs/namespace.c:1027 [inline]
do_new_mount fs/namespace.c:2518 [inline]
do_mount+0x564/0x3070 fs/namespace.c:2848
ksys_mount+0x12d/0x140 fs/namespace.c:3064
__do_sys_mount fs/namespace.c:3078 [inline]
__se_sys_mount fs/namespace.c:3075 [inline]
__x64_sys_mount+0xbe/0x150 fs/namespace.c:3075
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4404a9
RSP: 002b:00007fffca04f5f8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00000000004404a9
RDX: 00000000004a1d2c RSI: 0000000020000080 RDI: 00000000200000c0
RBP: 0030656c69662f2e R08: 00007fffca04f610 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000401d90
R13: 0000000000401e20 R14: 0000000000000000 R15: 0000000000000000
6da6c0db5316275015e8cc2959f12a17584aeb64 (Sun Apr 29 21:17:42 2018 +0000)
Linux v4.17-rc3
So far this crash happened 2 times on upstream.
C reproducer: https://syzkaller.appspot.com/x/repro.c?id=5078600311111680
syzkaller reproducer:
https://syzkaller.appspot.com/x/repro.syz?id=5938566311968768
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=6326042692157440
Kernel config:
https://syzkaller.appspot.com/x/.config?id=6493557782959164711
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+3337db...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed.
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00000000004404a9
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+3337db...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed.
RDX: 00000000004a1d2c RSI: 0000000020000080 RDI: 00000000200000c0
RBP: 0030656c69662f2e R08: 00007fffca04f610 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000401d90
R13: 0000000000401e20 R14: 0000000000000000 R15: 0000000000000000
WARNING: CPU: 1 PID: 4539 at block/genhd.c:685
__device_add_disk+0x104a/0x1340 block/genhd.c:685
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 4539 Comm: syz-executor708 Not tainted 4.17.0-rc3+ #25
Kernel panic - not syncing: panic_on_warn set ...
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+0x1b9/0x294 lib/dump_stack.c:113
panic+0x22f/0x4de kernel/panic.c:184
__warn.cold.8+0x163/0x1b3 kernel/panic.c:536
report_bug+0x252/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x1de/0x490 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:992
RIP: 0010:__device_add_disk+0x104a/0x1340 block/genhd.c:685
RSP: 0018:ffff8801ad26f4e0 EFLAGS: 00010293
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1b9/0x294 lib/dump_stack.c:113
panic+0x22f/0x4de kernel/panic.c:184
__warn.cold.8+0x163/0x1b3 kernel/panic.c:536
report_bug+0x252/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x1de/0x490 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:992
RIP: 0010:__device_add_disk+0x104a/0x1340 block/genhd.c:685
RAX: ffff8801d908e380 RBX: ffff8801d95d8e80 RCX: ffffffff83437c33
RDX: 0000000000000000 RSI: ffffffff83437d6a RDI: 0000000000000005
RBP: ffff8801ad26f6b0 R08: ffff8801d908e380 R09: 0000000000000006
R10: ffff8801d908e380 R11: 0000000000000000 R12: 00000000fffffff4
R13: ffff8801ad26f688 R14: ffff8801d95d93e0 R15: ffff8801d95d8e84
device_add_disk+0x22/0x30 block/genhd.c:705
add_disk include/linux/genhd.h:397 [inline]
loop_add+0x70b/0x9c0 drivers/block/loop.c:1895
add_disk include/linux/genhd.h:397 [inline]
loop_probe+0x185/0x1c0 drivers/block/loop.c:1967
kobj_lookup+0x269/0x460 drivers/base/map.c:124
get_gendisk+0x4c/0x380 block/genhd.c:813
bdev_get_gendisk fs/block_dev.c:1063 [inline]
bd_start_claiming fs/block_dev.c:1118 [inline]
blkdev_get+0x16a/0xb30 fs/block_dev.c:1604
blkdev_get_by_path+0x5c/0xe0 fs/block_dev.c:1689
mount_bdev+0x5d/0x3e0 fs/super.c:1122
fuse_mount_blk+0x34/0x40 fs/fuse/inode.c:1222
mount_fs+0xae/0x328 fs/super.c:1267
vfs_kern_mount.part.34+0xd4/0x4d0 fs/namespace.c:1037
vfs_kern_mount fs/namespace.c:1027 [inline]
do_new_mount fs/namespace.c:2518 [inline]
do_mount+0x564/0x3070 fs/namespace.c:2848
ksys_mount+0x12d/0x140 fs/namespace.c:3064
__do_sys_mount fs/namespace.c:3078 [inline]
__se_sys_mount fs/namespace.c:3075 [inline]
__x64_sys_mount+0xbe/0x150 fs/namespace.c:3075
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4404a9
RSP: 002b:00007fffca04f5f8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00000000004404a9
RDX: 00000000004a1d2c RSI: 0000000020000080 RDI: 00000000200000c0
RBP: 0030656c69662f2e R08: 00007fffca04f610 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000401d90
R13: 0000000000401e20 R14: 0000000000000000 R15: 0000000000000000
syzbot
Nov 26, 2019, 5:16:02 AM11/26/19
to akinob...@gmail.com, ak...@linux-foundation.org, ax...@kernel.dk, dvy...@google.com, gre...@linuxfoundation.org, linux...@vger.kernel.org, linux-...@vger.kernel.org, mho...@kernel.org, syzkall...@googlegroups.com, torv...@linux-foundation.org
syzbot has bisected this bug to:
commit e41d58185f1444368873d4d7422f7664a68be61d
Author: Dmitry Vyukov <dvy...@google.com>
Date: Wed Jul 12 21:34:35 2017 +0000
fault-inject: support systematic fault injection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17889f5ae00000
start commit: 6da6c0db Linux v4.17-rc3
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14489f5ae00000
console output: https://syzkaller.appspot.com/x/log.txt?x=10489f5ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5a1dc06635c10d27
dashboard link: https://syzkaller.appspot.com/bug?extid=3337db851ace689ceb50
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15191837800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120af5c7800000
Reported-by: syzbot+3337db...@syzkaller.appspotmail.com
Fixes: e41d58185f14 ("fault-inject: support systematic fault injection")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit e41d58185f1444368873d4d7422f7664a68be61d
Author: Dmitry Vyukov <dvy...@google.com>
Date: Wed Jul 12 21:34:35 2017 +0000
fault-inject: support systematic fault injection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17889f5ae00000
start commit: 6da6c0db Linux v4.17-rc3
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14489f5ae00000
console output: https://syzkaller.appspot.com/x/log.txt?x=10489f5ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5a1dc06635c10d27
dashboard link: https://syzkaller.appspot.com/bug?extid=3337db851ace689ceb50
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15191837800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120af5c7800000
Reported-by: syzbot+3337db...@syzkaller.appspotmail.com
Fixes: e41d58185f14 ("fault-inject: support systematic fault injection")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages