WARNING in inc_nlink
15 views
Skip to first unread message
syzbot
Mar 22, 2020, 5:07:17 AM3/22/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=122b4f55e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=e119c3cedf831cd93c5b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+e119c3...@syzkaller.appspotmail.com
MINIX-fs: mounting unchecked file system, running fsck is recommended
MINIX-fs: mounting unchecked file system, running fsck is recommended
------------[ cut here ]------------
WARNING: CPU: 1 PID: 26577 at fs/inode.c:341 inc_nlink+0x113/0x130 fs/inode.c:341
netlink: 32 bytes leftover after parsing attributes in process `syz-executor.1'.
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 26577 Comm: syz-executor.5 Not tainted 4.14.174-syzkaller #0
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+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:inc_nlink+0x113/0x130 fs/inode.c:341
RSP: 0018:ffff8881d9b0fdb0 EFLAGS: 00010212
RAX: 0000000000040000 RBX: ffff888099af2180 RCX: ffffc90005e24000
RDX: 0000000000000974 RSI: ffffffff8190edd3 RDI: ffff888099af2258
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000002
R10: ffffed103b361f8e R11: 0000000000000003 R12: ffff888099af21c8
R13: ffff888096649e40 R14: ffff888096649e98 R15: 0000000000000000
inode_inc_link_count include/linux/fs.h:2034 [inline]
minix_mkdir+0x5a/0x160 fs/minix/namei.c:121
vfs_mkdir+0x3af/0x620 fs/namei.c:3849
SYSC_mkdirat fs/namei.c:3872 [inline]
SyS_mkdirat fs/namei.c:3856 [inline]
SYSC_mkdir fs/namei.c:3883 [inline]
SyS_mkdir+0x1bc/0x210 fs/namei.c:3881
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45c849
RSP: 002b:00007fab61c78c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007fab61c796d4 RCX: 000000000045c849
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 0000000020000400
RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000072c R14: 00000000004c230d R15: 000000000076bf0c
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following crash on:
HEAD commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=122b4f55e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=e119c3cedf831cd93c5b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+e119c3...@syzkaller.appspotmail.com
MINIX-fs: mounting unchecked file system, running fsck is recommended
MINIX-fs: mounting unchecked file system, running fsck is recommended
------------[ cut here ]------------
WARNING: CPU: 1 PID: 26577 at fs/inode.c:341 inc_nlink+0x113/0x130 fs/inode.c:341
netlink: 32 bytes leftover after parsing attributes in process `syz-executor.1'.
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 26577 Comm: syz-executor.5 Not tainted 4.14.174-syzkaller #0
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+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:inc_nlink+0x113/0x130 fs/inode.c:341
RSP: 0018:ffff8881d9b0fdb0 EFLAGS: 00010212
RAX: 0000000000040000 RBX: ffff888099af2180 RCX: ffffc90005e24000
RDX: 0000000000000974 RSI: ffffffff8190edd3 RDI: ffff888099af2258
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000002
R10: ffffed103b361f8e R11: 0000000000000003 R12: ffff888099af21c8
R13: ffff888096649e40 R14: ffff888096649e98 R15: 0000000000000000
inode_inc_link_count include/linux/fs.h:2034 [inline]
minix_mkdir+0x5a/0x160 fs/minix/namei.c:121
vfs_mkdir+0x3af/0x620 fs/namei.c:3849
SYSC_mkdirat fs/namei.c:3872 [inline]
SyS_mkdirat fs/namei.c:3856 [inline]
SYSC_mkdir fs/namei.c:3883 [inline]
SyS_mkdir+0x1bc/0x210 fs/namei.c:3881
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45c849
RSP: 002b:00007fab61c78c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007fab61c796d4 RCX: 000000000045c849
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 0000000020000400
RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000072c R14: 00000000004c230d R15: 000000000076bf0c
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Mar 22, 2020, 5:30:14 AM3/22/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following crash on:
HEAD commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=165c318de00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12106939e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+e119c3...@syzkaller.appspotmail.com
audit: type=1400 audit(1584869240.881:36): avc: denied { map } for pid=7552 comm="syz-executor738" path="/root/syz-executor738797920" dev="sda1" ino=16483 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7552 at fs/inode.c:341 inc_nlink+0x113/0x130 fs/inode.c:341
RAX: ffff88808cc28280 RBX: ffff888095d15960 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880a9c378c0 RDI: ffff888095d15a38
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888095d159a8
R13: ffff8880a9c378c0 R14: ffff8880a9c37918 R15: 0000000000000000
RSP: 002b:00007fff49172218 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007fff49172220 RCX: 00000000004449f9
R10: 00007fff491720f0 R11: 0000000000000246 R12: 0000000000402660
R13: 00000000004026f0 R14: 0000000000000000 R15: 0000000000000000
HEAD commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=e119c3cedf831cd93c5b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156cf3f9e00000
dashboard link: https://syzkaller.appspot.com/bug?extid=e119c3cedf831cd93c5b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12106939e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+e119c3...@syzkaller.appspotmail.com
MINIX-fs: mounting unchecked file system, running fsck is recommended
audit: type=1400 audit(1584869240.931:37): avc: denied { associate } for pid=7552 comm="syz-executor738" name="file0" scontext=unconfined_u:object_r:unlabeled_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7552 at fs/inode.c:341 inc_nlink+0x113/0x130 fs/inode.c:341
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 7552 Comm: syz-executor738 Not tainted 4.14.174-syzkaller #0
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+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:inc_nlink+0x113/0x130 fs/inode.c:341
RSP: 0018:ffff888077fd7db0 EFLAGS: 00010297
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:inc_nlink+0x113/0x130 fs/inode.c:341
RAX: ffff88808cc28280 RBX: ffff888095d15960 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880a9c378c0 RDI: ffff888095d15a38
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888095d159a8
R13: ffff8880a9c378c0 R14: ffff8880a9c37918 R15: 0000000000000000
inode_inc_link_count include/linux/fs.h:2034 [inline]
minix_mkdir+0x5a/0x160 fs/minix/namei.c:121
vfs_mkdir+0x3af/0x620 fs/namei.c:3849
SYSC_mkdirat fs/namei.c:3872 [inline]
SyS_mkdirat fs/namei.c:3856 [inline]
SYSC_mkdir fs/namei.c:3883 [inline]
SyS_mkdir+0x1bc/0x210 fs/namei.c:3881
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x4449f9
minix_mkdir+0x5a/0x160 fs/minix/namei.c:121
vfs_mkdir+0x3af/0x620 fs/namei.c:3849
SYSC_mkdirat fs/namei.c:3872 [inline]
SyS_mkdirat fs/namei.c:3856 [inline]
SYSC_mkdir fs/namei.c:3883 [inline]
SyS_mkdir+0x1bc/0x210 fs/namei.c:3881
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RSP: 002b:00007fff49172218 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007fff49172220 RCX: 00000000004449f9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 0000000020000400
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000400de0
R10: 00007fff491720f0 R11: 0000000000000246 R12: 0000000000402660
R13: 00000000004026f0 R14: 0000000000000000 R15: 0000000000000000
syzbot
Mar 23, 2020, 3:48:17 AM3/23/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 14cfdbd3 Linux 4.19.112
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13af65b1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=48ea0e0a21a4900f
dashboard link: https://syzkaller.appspot.com/bug?extid=ba2febbc0330db7925b6
overlayfs: conflicting lowerdir path
------------[ cut here ]------------
WARNING: CPU: 0 PID: 18423 at fs/inode.c:342 inc_nlink.cold+0x11/0x18 fs/inode.c:342
dump_stack+0x188/0x20d lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x46 kernel/panic.c:541
report_bug+0x262/0x2a0 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+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1037
RIP: 0010:inc_nlink.cold+0x11/0x18 fs/inode.c:342
Code: cb b9 ff 44 89 e0 5b 5d 41 5c c3 e8 00 92 ef ff eb c3 e8 09 92 ef ff eb 8e e8 82 cb b9 ff 48 c7 c7 80 ce 74 87 e8 6f e8 a4 ff <0f> 0b e9 28 86 ff ff e8 6a cb b9 ff 48 8d 7b 40 b8 ff ff 37 00 48
RSP: 0018:ffff888058f67d88 EFLAGS: 00010282
RAX: 0000000000000024 RBX: ffff888056fbc568 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8152d3a1 RDI: ffffed100b1ecfa3
RBP: 0000000000000000 R08: 0000000000000024 R09: ffffed1015cc5079
R10: ffffed1015cc5078 R11: ffff8880ae6283c7 R12: ffff888056fbc5b0
R13: ffff8880933f1c60 R14: ffff8880933f1cb8 R15: 0000000000000000
inode_inc_link_count include/linux/fs.h:2097 [inline]
minix_mkdir+0x71/0x1b0 fs/minix/namei.c:117
vfs_mkdir+0x419/0x690 fs/namei.c:3819
do_mkdirat+0x21e/0x280 fs/namei.c:3842
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45c849
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffa9a504c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007ffa9a5056d4 RCX: 000000000045c849
RDX: 0000000000000050 RSI: 0000000020000040 RDI: 0000000000000003
RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000072d R14: 00000000004c9f0b R15: 000000000076bf0c
syzbot found the following crash on:
HEAD commit: 14cfdbd3 Linux 4.19.112
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13af65b1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=48ea0e0a21a4900f
dashboard link: https://syzkaller.appspot.com/bug?extid=ba2febbc0330db7925b6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+ba2feb...@syzkaller.appspotmail.com
overlayfs: conflicting lowerdir path
MINIX-fs: mounting unchecked file system, running fsck is recommended
MINIX-fs: bad superblock or unable to read bitmaps
------------[ cut here ]------------
WARNING: CPU: 0 PID: 18423 at fs/inode.c:342 inc_nlink.cold+0x11/0x18 fs/inode.c:342
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 18423 Comm: syz-executor.2 Not tainted 4.19.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
Call Trace:
dump_stack+0x188/0x20d lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x46 kernel/panic.c:541
report_bug+0x262/0x2a0 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+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1037
RIP: 0010:inc_nlink.cold+0x11/0x18 fs/inode.c:342
Code: cb b9 ff 44 89 e0 5b 5d 41 5c c3 e8 00 92 ef ff eb c3 e8 09 92 ef ff eb 8e e8 82 cb b9 ff 48 c7 c7 80 ce 74 87 e8 6f e8 a4 ff <0f> 0b e9 28 86 ff ff e8 6a cb b9 ff 48 8d 7b 40 b8 ff ff 37 00 48
RSP: 0018:ffff888058f67d88 EFLAGS: 00010282
RAX: 0000000000000024 RBX: ffff888056fbc568 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8152d3a1 RDI: ffffed100b1ecfa3
RBP: 0000000000000000 R08: 0000000000000024 R09: ffffed1015cc5079
R10: ffffed1015cc5078 R11: ffff8880ae6283c7 R12: ffff888056fbc5b0
R13: ffff8880933f1c60 R14: ffff8880933f1cb8 R15: 0000000000000000
inode_inc_link_count include/linux/fs.h:2097 [inline]
minix_mkdir+0x71/0x1b0 fs/minix/namei.c:117
vfs_mkdir+0x419/0x690 fs/namei.c:3819
do_mkdirat+0x21e/0x280 fs/namei.c:3842
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45c849
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffa9a504c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007ffa9a5056d4 RCX: 000000000045c849
RDX: 0000000000000050 RSI: 0000000020000040 RDI: 0000000000000003
RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000072d R14: 00000000004c9f0b R15: 000000000076bf0c
Kernel Offset: disabled
Rebooting in 86400 seconds..
Rebooting in 86400 seconds..
syzbot
Mar 23, 2020, 4:09:15 AM3/23/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following crash on:
HEAD commit: 14cfdbd3 Linux 4.19.112
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1662e8c5e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=151e18ade00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+ba2feb...@syzkaller.appspotmail.com
audit: type=1400 audit(1584950741.199:36): avc: denied { map } for pid=8253 comm="syz-executor602" path="/root/syz-executor602440770" dev="sda1" ino=16483 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
audit: type=1400 audit(1584950741.239:37): avc: denied { associate } for pid=8253 comm="syz-executor602" name="file0" scontext=unconfined_u:object_r:unlabeled_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1
WARNING: CPU: 1 PID: 8253 at fs/inode.c:342 inc_nlink.cold+0x11/0x18 fs/inode.c:342
RAX: 0000000000000024 RBX: ffff888094ba8950 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8152d3a1 RDI: ffffed1013e97fa3
RBP: 0000000000000000 R08: 0000000000000024 R09: ffffed1015ce5079
R10: ffffed1015ce5078 R11: ffff8880ae7283c7 R12: ffff888094ba8998
R13: ffff88807988e1e0 R14: ffff88807988e238 R15: 0000000000000000
Code: 0d d8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 db d7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fff51001b58 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fff51001b60 RCX: 0000000000444a69
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004026d0
R13: 0000000000402760 R14: 0000000000000000 R15: 0000000000000000
HEAD commit: 14cfdbd3 Linux 4.19.112
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=48ea0e0a21a4900f
dashboard link: https://syzkaller.appspot.com/bug?extid=ba2febbc0330db7925b6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127a5e75e00000
dashboard link: https://syzkaller.appspot.com/bug?extid=ba2febbc0330db7925b6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=151e18ade00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+ba2feb...@syzkaller.appspotmail.com
MINIX-fs: mounting unchecked file system, running fsck is recommended
------------[ cut here ]------------
audit: type=1400 audit(1584950741.239:37): avc: denied { associate } for pid=8253 comm="syz-executor602" name="file0" scontext=unconfined_u:object_r:unlabeled_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1
WARNING: CPU: 1 PID: 8253 at fs/inode.c:342 inc_nlink.cold+0x11/0x18 fs/inode.c:342
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 8253 Comm: syz-executor602 Not tainted 4.19.112-syzkaller #0
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+0x188/0x20d lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x46 kernel/panic.c:541
report_bug+0x262/0x2a0 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+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1037
RIP: 0010:inc_nlink.cold+0x11/0x18 fs/inode.c:342
Code: cb b9 ff 44 89 e0 5b 5d 41 5c c3 e8 00 92 ef ff eb c3 e8 09 92 ef ff eb 8e e8 82 cb b9 ff 48 c7 c7 80 ce 74 87 e8 6f e8 a4 ff <0f> 0b e9 28 86 ff ff e8 6a cb b9 ff 48 8d 7b 40 b8 ff ff 37 00 48
RSP: 0018:ffff88809f4bfd88 EFLAGS: 00010282
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x188/0x20d lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x46 kernel/panic.c:541
report_bug+0x262/0x2a0 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+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1037
RIP: 0010:inc_nlink.cold+0x11/0x18 fs/inode.c:342
Code: cb b9 ff 44 89 e0 5b 5d 41 5c c3 e8 00 92 ef ff eb c3 e8 09 92 ef ff eb 8e e8 82 cb b9 ff 48 c7 c7 80 ce 74 87 e8 6f e8 a4 ff <0f> 0b e9 28 86 ff ff e8 6a cb b9 ff 48 8d 7b 40 b8 ff ff 37 00 48
RAX: 0000000000000024 RBX: ffff888094ba8950 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8152d3a1 RDI: ffffed1013e97fa3
RBP: 0000000000000000 R08: 0000000000000024 R09: ffffed1015ce5079
R10: ffffed1015ce5078 R11: ffff8880ae7283c7 R12: ffff888094ba8998
R13: ffff88807988e1e0 R14: ffff88807988e238 R15: 0000000000000000
inode_inc_link_count include/linux/fs.h:2097 [inline]
minix_mkdir+0x71/0x1b0 fs/minix/namei.c:117
vfs_mkdir+0x419/0x690 fs/namei.c:3819
do_mkdirat+0x21e/0x280 fs/namei.c:3842
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x444a69
minix_mkdir+0x71/0x1b0 fs/minix/namei.c:117
vfs_mkdir+0x419/0x690 fs/namei.c:3819
do_mkdirat+0x21e/0x280 fs/namei.c:3842
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Code: 0d d8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 db d7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fff51001b58 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fff51001b60 RCX: 0000000000444a69
RDX: 0000000000000050 RSI: 0000000020000040 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000400e50 R09: 0000000000400e50
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004026d0
R13: 0000000000402760 R14: 0000000000000000 R15: 0000000000000000
syzbot
Sep 10, 2020, 7:38:06 PM9/10/20
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit 12490f06ef084bc34f5e5dbda104aa034e376f2e
Author: Eric Biggers <ebig...@google.com>
Date: Wed Aug 12 01:35:27 2020 +0000
fs/minix: don't allow getting deleted inodes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b40f71900000
start commit: a41ba30d Linux 4.14.181
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=c5458e9cda81cf95
dashboard link: https://syzkaller.appspot.com/bug?extid=e119c3cedf831cd93c5b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156d067e100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167e3ce2100000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/minix: don't allow getting deleted inodes
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit 12490f06ef084bc34f5e5dbda104aa034e376f2e
Author: Eric Biggers <ebig...@google.com>
Date: Wed Aug 12 01:35:27 2020 +0000
fs/minix: don't allow getting deleted inodes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b40f71900000
start commit: a41ba30d Linux 4.14.181
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=c5458e9cda81cf95
dashboard link: https://syzkaller.appspot.com/bug?extid=e119c3cedf831cd93c5b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156d067e100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167e3ce2100000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/minix: don't allow getting deleted inodes
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot
Sep 18, 2020, 2:54:06 AM9/18/20
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit 169f7f37bd6b0bb91242099cc261219791067d5c
Author: Eric Biggers <ebig...@google.com>
Date: Wed Aug 12 01:35:27 2020 +0000
fs/minix: don't allow getting deleted inodes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1537448d900000
Date: Wed Aug 12 01:35:27 2020 +0000
fs/minix: don't allow getting deleted inodes
start commit: 1bab61d3 Linux 4.19.124
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=e95e3ce854b90b1b
dashboard link: https://syzkaller.appspot.com/bug?extid=ba2febbc0330db7925b6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c12b81100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108bad6e100000
Reply all
Reply to author
Forward
0 new messages