Hello,
syzbot found the following issue on:
HEAD commit: 805ba04cb7cc Merge tag 'mips_6.14' of git://
git.kernel.org..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1479e924580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=e0b04511e541daf8
dashboard link:
https://syzkaller.appspot.com/bug?extid=8ab946a62f8db94526f7
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [
h...@lst.de jl...@evilplan.org linux-...@vger.kernel.org linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/4316bfd58209/disk-805ba04c.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/1ccf68febae6/vmlinux-805ba04c.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/7dff5c73e93a/bzImage-805ba04c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+8ab946...@syzkaller.appspotmail.com
Oops: general protection fault, probably for non-canonical address 0xdffffc000000000a: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000050-0x0000000000000057]
CPU: 0 UID: 0 PID: 8610 Comm: syz.2.731 Not tainted 6.13.0-syzkaller-08291-g805ba04cb7cc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:__lock_acquire+0xe4/0x3c40 kernel/locking/lockdep.c:5091
Code: 08 84 d2 0f 85 15 14 00 00 44 8b 0d 7a 4f ca 0e 45 85 c9 0f 84 b4 0e 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 <80> 3c 02 00 0f 85 96 2c 00 00 49 8b 04 24 48 3d a0 27 79 93 0f 84
RSP: 0018:ffffc90005216fb0 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000001 RCX: 0000000000000002
RDX: 000000000000000a RSI: 1ffff92000a42e08 RDI: 0000000000000050
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff905ff717 R11: 0000000000000005 R12: 0000000000000050
R13: ffff888027c0da00 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3fe84d56c0 CR3: 00000000661e0000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5851
seqcount_lockdep_reader_access include/linux/seqlock.h:72 [inline]
path_init+0x14a5/0x1ab0 fs/namei.c:2554
path_openat+0x192/0x2d80 fs/namei.c:3982
do_filp_open+0x20c/0x470 fs/namei.c:4014
file_open_name+0x2a4/0x450 fs/open.c:1372
filp_open+0x4b/0x80 fs/open.c:1392
target_core_item_dbroot_store+0x10d/0x2e0 drivers/target/target_core_configfs.c:134
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x2f6/0x4b0 fs/configfs/file.c:229
__kernel_write_iter+0x318/0xa90 fs/read_write.c:612
__kernel_write+0xf6/0x140 fs/read_write.c:632
do_acct_process+0xd11/0x1530 kernel/acct.c:539
acct_pin_kill+0x2d/0x100 kernel/acct.c:192
pin_kill+0x194/0x7c0 fs/fs_pin.c:44
mnt_pin_kill+0x61/0x1e0 fs/fs_pin.c:81
cleanup_mnt+0x3ac/0x450 fs/namespace.c:1406
task_work_run+0x14e/0x250 kernel/task_work.c:227
exit_task_work include/linux/task_work.h:40 [inline]
do_exit+0xad8/0x2d70 kernel/exit.c:938
do_group_exit+0xd3/0x2a0 kernel/exit.c:1087
get_signal+0x2576/0x2610 kernel/signal.c:3036
arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
irqentry_exit_to_user_mode+0x13f/0x280 kernel/entry/common.c:231
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
RIP: 0033:0x7f1ae758cdb1
Code: Unable to access opcode bytes at 0x7f1ae758cd87.
RSP: 002b:ffffffffffffffa0 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f1ae77a5fa0 RCX: 00007f1ae758cda9
RDX: 0000000000000000 RSI: ffffffffffffffa0 RDI: 000000008088a211
RBP: 00007f1ae760e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f1ae77a5fa0 R15: 00007ffd911a86d8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__lock_acquire+0xe4/0x3c40 kernel/locking/lockdep.c:5091
Code: 08 84 d2 0f 85 15 14 00 00 44 8b 0d 7a 4f ca 0e 45 85 c9 0f 84 b4 0e 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 <80> 3c 02 00 0f 85 96 2c 00 00 49 8b 04 24 48 3d a0 27 79 93 0f 84
RSP: 0018:ffffc90005216fb0 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000001 RCX: 0000000000000002
RDX: 000000000000000a RSI: 1ffff92000a42e08 RDI: 0000000000000050
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff905ff717 R11: 0000000000000005 R12: 0000000000000050
R13: ffff888027c0da00 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3fe84d56c0 CR3: 00000000661e0000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 08 84 d2 0f 85 15 14 or %al,0x1415850f(%rdx,%rdx,8)
7: 00 00 add %al,(%rax)
9: 44 8b 0d 7a 4f ca 0e mov 0xeca4f7a(%rip),%r9d # 0xeca4f8a
10: 45 85 c9 test %r9d,%r9d
13: 0f 84 b4 0e 00 00 je 0xecd
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 4c 89 e2 mov %r12,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 96 2c 00 00 jne 0x2cca
34: 49 8b 04 24 mov (%r12),%rax
38: 48 3d a0 27 79 93 cmp $0xffffffff937927a0,%rax
3e: 0f .byte 0xf
3f: 84 .byte 0x84
---
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