From: syzbot <syzbot+a9ac3de1b5de5fb10efc@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: WARNING in inc_nlink
Date: Tue, 31 Mar 2020 10:21:12 -0700 [thread overview]
Message-ID: <000000000000519c8405a229cbc2@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: e595dd94 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16b2bc15e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=27392dd2975fd692
dashboard link: https://syzkaller.appspot.com/bug?extid=a9ac3de1b5de5fb10efc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d33183e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1076297be00000
Bisection is inconclusive: the bug happens on the oldest tested release.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=147487a3e00000
final crash: https://syzkaller.appspot.com/x/report.txt?x=167487a3e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=127487a3e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+a9ac3de1b5de5fb10efc@syzkaller.appspotmail.com
MINIX-fs: mounting unchecked file system, running fsck is recommended
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7042 at fs/inode.c:360 inc_nlink+0x144/0x160 fs/inode.c:360
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 7042 Comm: syz-executor911 Not tainted 5.6.0-rc7-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+0x2e3/0x75c kernel/panic.c:221
__warn.cold+0x2f/0x35 kernel/panic.c:582
report_bug+0x27b/0x2f0 lib/bug.c:195
fixup_bug arch/x86/kernel/traps.c:174 [inline]
fixup_bug arch/x86/kernel/traps.c:169 [inline]
do_error_trap+0x12b/0x220 arch/x86/kernel/traps.c:267
do_invalid_op+0x32/0x40 arch/x86/kernel/traps.c:286
invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1027
RIP: 0010:inc_nlink+0x144/0x160 fs/inode.c:360
Code: ff 4c 89 e7 e8 ed 99 ee ff e9 42 ff ff ff 4c 89 e7 e8 70 99 ee ff e9 fc fe ff ff 4c 89 e7 e8 63 99 ee ff eb d4 e8 5c d0 b1 ff <0f> 0b e9 6e ff ff ff e8 60 99 ee ff e9 44 ff ff ff e8 56 99 ee ff
RSP: 0018:ffffc90000ef7d88 EFLAGS: 00010293
RAX: ffff88808721c300 RBX: ffff888085dab990 RCX: ffffffff81c05430
RDX: 0000000000000000 RSI: ffffffff81c054c4 RDI: 0000000000000007
RBP: 0000000000000000 R08: ffff88808721c300 R09: ffffed1043789757
R10: ffffed1043789756 R11: ffff88821bc4bab3 R12: ffff888085dab9d8
R13: ffff888089848b80 R14: ffff888089848bd8 R15: 0000000000000000
inode_inc_link_count include/linux/fs.h:2199 [inline]
minix_mkdir+0x71/0x1b0 fs/minix/namei.c:117
vfs_mkdir+0x419/0x670 fs/namei.c:3889
do_mkdirat+0x21e/0x280 fs/namei.c:3912
do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x444a69
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:00007ffc41646e48 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007ffc41646e50 RCX: 0000000000444a69
RDX: 00000000000001ff RSI: 0000000020000080 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000400e50 R09: 0000000000400e50
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004026d0
R13: 0000000000402760 R14: 0000000000000000 R15: 0000000000000000
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 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
reply other threads:[~2020-03-31 17:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000519c8405a229cbc2@google.com \
--to=syzbot+a9ac3de1b5de5fb10efc@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.