kernel BUG in jfs_destroy_inode
9 views
Skip to first unread message
syzbot
Sep 25, 2022, 6:54:41 PM9/25/22
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 4edbf74132a4 Linux 4.14.294
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11aa17f8880000
kernel config: https://syzkaller.appspot.com/x/.config?x=94d4cf9c4e23980f
dashboard link: https://syzkaller.appspot.com/bug?extid=18028a7fa59ecdcf4eeb
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb8938880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10792e38880000
Downloadable assets:
disk image: https://storage.googleapis.com/b40da19b4827/disk-4edbf741.raw.xz
vmlinux: https://storage.googleapis.com/a36e39677c18/vmlinux-4edbf741.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+18028a...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
ERROR: (device loop0): xtSearch: XT_GETPAGE: xtree page corrupt
ERROR: (device loop0): xtTruncate: XT_GETPAGE: xtree page corrupt
------------[ cut here ]------------
kernel BUG at fs/jfs/super.c:138!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 7997 Comm: syz-executor275 Not tainted 4.14.294-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
task: ffff8880b3062300 task.stack: ffff8880b32c8000
RIP: 0010:jfs_destroy_inode+0x16f/0x1c0 fs/jfs/super.c:138
RSP: 0018:ffff8880b32cfb50 EFLAGS: 00010297
RAX: ffff8880b3062300 RBX: ffff88808d2e35a8 RCX: 1ffff1101660c576
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88808d2e35a8
RBP: ffff88808d2e3270 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880b3062300 R12: ffff8880b32cfc30
R13: ffff88808d2e3750 R14: ffffed1016659f86 R15: ffff88808d2e35a8
FS: 0000555556b92300(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2525ffd1d0 CR3: 00000000afdd6000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
destroy_inode+0xb9/0x110 fs/inode.c:267
dispose_list+0x109/0x1e0 fs/inode.c:590
evict_inodes+0x2cd/0x3a0 fs/inode.c:640
generic_shutdown_super+0xb3/0x370 fs/super.c:438
kill_block_super+0x95/0xe0 fs/super.c:1161
deactivate_locked_super+0x6c/0xd0 fs/super.c:319
deactivate_super+0x7f/0xa0 fs/super.c:350
cleanup_mnt+0x186/0x2c0 fs/namespace.c:1183
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa44/0x2850 kernel/exit.c:868
do_group_exit+0x100/0x2e0 kernel/exit.c:965
SYSC_exit_group kernel/exit.c:976 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:974
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f2525f78699
RSP: 002b:00007ffc64861998 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f2525ffc330 RCX: 00007f2525f78699
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2525ffc330
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
Code: e1 1c ff 4c 89 ef e8 f1 fb eb 04 48 8d bb d0 01 00 00 5b 48 c7 c6 20 67 38 82 5d 41 5c 41 5d 41 5e e9 86 88 0e ff e8 f1 e0 1c ff <0f> 0b 4c 89 e7 e8 37 99 46 ff e9 06 ff ff ff 4c 89 e7 e8 da 9b
RIP: jfs_destroy_inode+0x16f/0x1c0 fs/jfs/super.c:138 RSP: ffff8880b32cfb50
---[ end trace b12234e47b357851 ]---
---
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 found the following issue on:
HEAD commit: 4edbf74132a4 Linux 4.14.294
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11aa17f8880000
kernel config: https://syzkaller.appspot.com/x/.config?x=94d4cf9c4e23980f
dashboard link: https://syzkaller.appspot.com/bug?extid=18028a7fa59ecdcf4eeb
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb8938880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10792e38880000
Downloadable assets:
disk image: https://storage.googleapis.com/b40da19b4827/disk-4edbf741.raw.xz
vmlinux: https://storage.googleapis.com/a36e39677c18/vmlinux-4edbf741.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+18028a...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
ERROR: (device loop0): xtSearch: XT_GETPAGE: xtree page corrupt
ERROR: (device loop0): xtTruncate: XT_GETPAGE: xtree page corrupt
------------[ cut here ]------------
kernel BUG at fs/jfs/super.c:138!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 7997 Comm: syz-executor275 Not tainted 4.14.294-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
task: ffff8880b3062300 task.stack: ffff8880b32c8000
RIP: 0010:jfs_destroy_inode+0x16f/0x1c0 fs/jfs/super.c:138
RSP: 0018:ffff8880b32cfb50 EFLAGS: 00010297
RAX: ffff8880b3062300 RBX: ffff88808d2e35a8 RCX: 1ffff1101660c576
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88808d2e35a8
RBP: ffff88808d2e3270 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880b3062300 R12: ffff8880b32cfc30
R13: ffff88808d2e3750 R14: ffffed1016659f86 R15: ffff88808d2e35a8
FS: 0000555556b92300(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2525ffd1d0 CR3: 00000000afdd6000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
destroy_inode+0xb9/0x110 fs/inode.c:267
dispose_list+0x109/0x1e0 fs/inode.c:590
evict_inodes+0x2cd/0x3a0 fs/inode.c:640
generic_shutdown_super+0xb3/0x370 fs/super.c:438
kill_block_super+0x95/0xe0 fs/super.c:1161
deactivate_locked_super+0x6c/0xd0 fs/super.c:319
deactivate_super+0x7f/0xa0 fs/super.c:350
cleanup_mnt+0x186/0x2c0 fs/namespace.c:1183
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa44/0x2850 kernel/exit.c:868
do_group_exit+0x100/0x2e0 kernel/exit.c:965
SYSC_exit_group kernel/exit.c:976 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:974
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f2525f78699
RSP: 002b:00007ffc64861998 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f2525ffc330 RCX: 00007f2525f78699
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2525ffc330
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
Code: e1 1c ff 4c 89 ef e8 f1 fb eb 04 48 8d bb d0 01 00 00 5b 48 c7 c6 20 67 38 82 5d 41 5c 41 5d 41 5e e9 86 88 0e ff e8 f1 e0 1c ff <0f> 0b 4c 89 e7 e8 37 99 46 ff e9 06 ff ff ff 4c 89 e7 e8 da 9b
RIP: jfs_destroy_inode+0x16f/0x1c0 fs/jfs/super.c:138 RSP: ffff8880b32cfb50
---[ end trace b12234e47b357851 ]---
---
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
Sep 25, 2022, 9:02:40 PM9/25/22
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
syzbot found the following issue on:
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14607804880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=919f232ff79b15f48913
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16eecf54880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16245edf080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
IPVS: ftp: loaded support on port[0] = 21
ERROR: (device loop0): xtSearch: XT_GETPAGE: xtree page corrupt
ERROR: (device loop0): xtTruncate: XT_GETPAGE: xtree page corrupt
------------[ cut here ]------------
kernel BUG at fs/jfs/super.c:138!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
RIP: 0010:jfs_destroy_inode+0x18d/0x1e0 fs/jfs/super.c:138
Code: 4c 89 e2 48 c1 ea 03 0f b6 04 02 4c 89 e2 83 e2 07 38 d0 7f 04 84 c0 75 37 c6 83 83 fc ff ff ff e9 16 ff ff ff e8 93 12 f0 fe <0f> 0b 4c 89 e7 e8 29 ed 25 ff e9 e8 fe ff ff 48 89 ef e8 6c ef 25
RSP: 0018:ffff8880b3287ab8 EFLAGS: 00010293
RAX: ffff8880b0cc65c0 RBX: ffff88808b4045a8 RCX: ffffffff81a93820
RDX: 0000000000000000 RSI: ffffffff827272dd RDI: ffff88808b4045a8
RBP: ffff88808b404270 R08: 00000000beff0c58 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8880b3287b98 R14: ffff88808b404748 R15: ffff88808b4045a8
FS: 0000555555618300(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3ade6661d0 CR3: 0000000094f75000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
destroy_inode+0xb9/0x110 fs/inode.c:268
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
dispose_list+0x124/0x1f0 fs/inode.c:594
evict_inodes+0x341/0x430 fs/inode.c:644
generic_shutdown_super+0xb3/0x370 fs/super.c:448
kill_block_super+0x97/0xf0 fs/super.c:1185
deactivate_locked_super+0x94/0x160 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1a8/0x290 fs/namespace.c:1098
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xbf3/0x2be0 kernel/exit.c:870
do_group_exit+0x125/0x310 kernel/exit.c:967
__do_sys_exit_group kernel/exit.c:978 [inline]
__se_sys_exit_group kernel/exit.c:976 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:976
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f3ade5e1699
Code: Bad RIP value.
RSP: 002b:00007ffcfc87ea48 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f3ade665330 RCX: 00007f3ade5e1699
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f3ade665330
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 0000000000000000
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
Modules linked in:
---[ end trace 83e2c63f8cbc8a3c ]---
RIP: 0010:jfs_destroy_inode+0x18d/0x1e0 fs/jfs/super.c:138
Code: 4c 89 e2 48 c1 ea 03 0f b6 04 02 4c 89 e2 83 e2 07 38 d0 7f 04 84 c0 75 37 c6 83 83 fc ff ff ff e9 16 ff ff ff e8 93 12 f0 fe <0f> 0b 4c 89 e7 e8 29 ed 25 ff e9 e8 fe ff ff 48 89 ef e8 6c ef 25
RSP: 0018:ffff8880b3287ab8 EFLAGS: 00010293
RAX: ffff8880b0cc65c0 RBX: ffff88808b4045a8 RCX: ffffffff81a93820
RDX: 0000000000000000 RSI: ffffffff827272dd RDI: ffff88808b4045a8
RBP: ffff88808b404270 R08: 00000000beff0c58 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8880b3287b98 R14: ffff88808b404748 R15: ffff88808b4045a8
FS: 0000555555618300(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3ab59a3018 CR3: 00000000a0f54000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Reply all
Reply to author
Forward
0 new messages