[moderation] [jfs?] general protection fault in jfs_error

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dd5a440a31fa Linux 6.9-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1517d354980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9d7ea7de0cb32587
dashboard link: https://syzkaller.appspot.com/bug?extid=d8f3a37a0d1065a1dce7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [jfs-dis...@lists.sourceforge.net linux-...@vger.kernel.org sha...@kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5f1a89860b95/disk-dd5a440a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/60884cc0d6ab/vmlinux-dd5a440a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fff740cfa7ce/bzImage-dd5a440a.xz

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

general protection fault, probably for non-canonical address 0xdffffc000000000a: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000050-0x0000000000000057]
CPU: 1 PID: 17026 Comm: syz-executor.1 Not tainted 6.9.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:sb_rdonly include/linux/fs.h:2234 [inline]
RIP: 0010:jfs_handle_error fs/jfs/super.c:66 [inline]
RIP: 0010:jfs_error+0x159/0x2e0 fs/jfs/super.c:98
Code: 08 48 c7 c7 00 e5 01 8c 48 89 74 24 08 4c 89 f9 e8 6c 6c 56 08 4d 8d 65 50 4d 89 e7 49 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <41> 80 3c 07 00 74 08 4c 89 e7 e8 78 56 d9 fe 49 8b 1c 24 48 89 de
RSP: 0018:ffffc9000d0676c0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: dffffc0000000000 RCX: 90587d9c49768c00
RDX: ffffc9000bbe5000 RSI: 000000000003d922 RDI: 000000000003d923
RBP: ffffc9000d0677d0 R08: ffffffff8176adac R09: 1ffff110172a519a
R10: dffffc0000000000 R11: ffffed10172a519b R12: 0000000000000050
R13: 0000000000000000 R14: 1ffff92001a0cee0 R15: 000000000000000a
FS: 00007fbed41776c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4d3780a000 CR3: 0000000025590000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xfee/0x1bb0 fs/jfs/namei.c:1243
vfs_rename+0xbdb/0xf00 fs/namei.c:4880
do_renameat2+0xd94/0x13f0 fs/namei.c:5037
__do_sys_renameat2 fs/namei.c:5071 [inline]
__se_sys_renameat2 fs/namei.c:5068 [inline]
__x64_sys_renameat2+0xd2/0xf0 fs/namei.c:5068
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbed347dca9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbed41770c8 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007fbed35abf80 RCX: 00007fbed347dca9
RDX: ffffffffffffff9c RSI: 0000000020000780 RDI: ffffffffffffff9c
RBP: 00007fbed34c947e R08: 0000000000000000 R09: 0000000000000000
R10: 00000000200007c0 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fbed35abf80 R15: 00007fff391ce8e8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:sb_rdonly include/linux/fs.h:2234 [inline]
RIP: 0010:jfs_handle_error fs/jfs/super.c:66 [inline]
RIP: 0010:jfs_error+0x159/0x2e0 fs/jfs/super.c:98
Code: 08 48 c7 c7 00 e5 01 8c 48 89 74 24 08 4c 89 f9 e8 6c 6c 56 08 4d 8d 65 50 4d 89 e7 49 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <41> 80 3c 07 00 74 08 4c 89 e7 e8 78 56 d9 fe 49 8b 1c 24 48 89 de
RSP: 0018:ffffc9000d0676c0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: dffffc0000000000 RCX: 90587d9c49768c00
RDX: ffffc9000bbe5000 RSI: 000000000003d922 RDI: 000000000003d923
RBP: ffffc9000d0677d0 R08: ffffffff8176adac R09: 1ffff110172a519a
R10: dffffc0000000000 R11: ffffed10172a519b R12: 0000000000000050
R13: 0000000000000000 R14: 1ffff92001a0cee0 R15: 000000000000000a
FS: 00007fbed41776c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffec5475268 CR3: 0000000025590000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 08 48 c7 or %cl,-0x39(%rax)
3: c7 00 e5 01 8c 48 movl $0x488c01e5,(%rax)
9: 89 74 24 08 mov %esi,0x8(%rsp)
d: 4c 89 f9 mov %r15,%rcx
10: e8 6c 6c 56 08 call 0x8566c81
15: 4d 8d 65 50 lea 0x50(%r13),%r12
19: 4d 89 e7 mov %r12,%r15
1c: 49 c1 ef 03 shr $0x3,%r15
20: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
27: fc ff df
* 2a: 41 80 3c 07 00 cmpb $0x0,(%r15,%rax,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 e7 mov %r12,%rdi
34: e8 78 56 d9 fe call 0xfed956b1
39: 49 8b 1c 24 mov (%r12),%rbx
3d: 48 89 de mov %rbx,%rsi


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup