WARNING in unlock_new_inode (2)

9 views
Skip to first unread message

syzbot

unread,
Oct 1, 2022, 3:57:36 AM10/1/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1222f5c4880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=5d4755233c99f936988d
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13657b18880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=124497ef080000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5d4755...@syzkaller.appspotmail.com

NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8107 at fs/inode.c:979 unlock_new_inode.cold+0x11/0x3f fs/inode.c:979
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8107 Comm: syz-executor890 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
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:1038
RIP: 0010:unlock_new_inode.cold+0x11/0x3f fs/inode.c:979
Code: b3 e8 bf bc 6d f9 48 c7 c7 80 b0 74 88 e8 1e ee fe ff 0f 0b e9 4a 70 b4 f9 e8 a7 bc 6d f9 48 c7 c7 80 b0 74 88 e8 06 ee fe ff <0f> 0b b8 ff ff 37 00 4c 89 e2 48 c1 ea 03 48 c1 e0 2a 80 3c 02 00
RSP: 0018:ffff8880965af7e0 EFLAGS: 00010286
RAX: 0000000000000024 RBX: ffff88808da89368 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1012cb5eee
RBP: 0000000000008000 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff88808da89438
R13: ffff88808da893f0 R14: 0000000000000000 R15: fffffffffffffffb
nilfs_new_inode+0x61f/0x760 fs/nilfs2/inode.c:399
nilfs_create fs/nilfs2/namei.c:85 [inline]
nilfs_create+0xfe/0x2f0 fs/nilfs2/namei.c:75
lookup_open+0x893/0x1a20 fs/namei.c:3235
do_last fs/namei.c:3327 [inline]
path_openat+0x1094/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f10c7ded339
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd2efa9778 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f10c7ded339
RDX: 000000000000275a RSI: 0000000020000140 RDI: 00000000ffffff9c
RBP: 00007f10c7dacba0 R08: 00005555566cd2c0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f10c7dacc30
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Oct 2, 2022, 12:48:36 AM10/2/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9d5c0b3a8e1a Linux 4.14.295
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14dd4f22880000
kernel config: https://syzkaller.appspot.com/x/.config?x=746c079015a92425
dashboard link: https://syzkaller.appspot.com/bug?extid=6212a8b4dbaa2c1dc977
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10fad2b8880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ebb722880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed6fcf5895a2/disk-9d5c0b3a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/341aa3534116/vmlinux-9d5c0b3a.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6212a8...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 7980 at fs/inode.c:967 unlock_new_inode+0x9a/0xc0 fs/inode.c:967
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 7980 Comm: syz-executor224 Not tainted 4.14.295-syzkaller #0
NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
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:964
RIP: 0010:unlock_new_inode+0x9a/0xc0 fs/inode.c:967
RSP: 0018:ffff88808c4678a8 EFLAGS: 00010297
RAX: ffff8880b32d6640 RBX: ffff88808debb368 RCX: 000000000000155e
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88808debb3f4
RBP: 0000000000000000 R08: ffffffff8b9ac5f0 R09: 000000000004057a
R10: ffff8880b32d6f68 R11: ffff8880b32d6640 R12: ffff88808debb440
R13: ffff88808debb3f0 R14: ffff888096e061c0 R15: ffff88808debb368
nilfs_new_inode+0x59f/0x6f0 fs/nilfs2/inode.c:408
nilfs_create fs/nilfs2/namei.c:94 [inline]
nilfs_create+0xd2/0x2a0 fs/nilfs2/namei.c:84
lookup_open+0x77a/0x1750 fs/namei.c:3241
do_last fs/namei.c:3334 [inline]
path_openat+0xe08/0x2970 fs/namei.c:3571
do_filp_open+0x179/0x3c0 fs/namei.c:3605
do_sys_open+0x296/0x410 fs/open.c:1081
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f938ed77339
RSP: 002b:00007ffd7e07b918 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f938ed77339
RDX: 000000000000275a RSI: 0000000020000140 RDI: 00000000ffffff9c
RBP: 00007f938ed36ba0 R08: 0000555556f2e2c0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f938ed36c30
Reply all
Reply to author
Forward
0 new messages