* [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (4)
@ 2025-10-23 21:21 syzbot
2025-10-23 21:34 ` Caleb Sander Mateos
2025-10-24 0:49 ` Jens Axboe
0 siblings, 2 replies; 5+ messages in thread
From: syzbot @ 2025-10-23 21:21 UTC (permalink / raw)
To: axboe, io-uring, kbusch, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: aaa9c3550b60 Add linux-next specific files for 20251022
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11880c92580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c8b911aebadf6410
dashboard link: https://syzkaller.appspot.com/bug?extid=a77f64386b3e1b2ebb51
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e73734580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=102f43e2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/44f7af9b7ca1/disk-aaa9c355.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9d09b0a9994d/vmlinux-aaa9c355.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ae729ccb2c5c/bzImage-aaa9c355.xz
The issue was bisected to:
commit 31dc41afdef21f264364288a30013b538c46152e
Author: Keith Busch <kbusch@kernel.org>
Date: Thu Oct 16 18:09:38 2025 +0000
io_uring: add support for IORING_SETUP_SQE_MIXED
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12eac614580000
final oops: https://syzkaller.appspot.com/x/report.txt?x=11eac614580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16eac614580000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a77f64386b3e1b2ebb51@syzkaller.appspotmail.com
Fixes: 31dc41afdef2 ("io_uring: add support for IORING_SETUP_SQE_MIXED")
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 0 UID: 0 PID: 6032 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:__io_uring_show_fdinfo io_uring/fdinfo.c:103 [inline]
RIP: 0010:io_uring_show_fdinfo+0x371/0x1840 io_uring/fdinfo.c:255
Code: 0f 85 29 04 00 00 45 8b 36 44 89 f7 44 89 ee e8 a5 ec 94 00 45 39 ee 76 11 e8 db ea 94 00 45 89 fd 4c 8b 3c 24 e9 c9 03 00 00 <80> 3b 00 45 89 fd 0f 85 17 04 00 00 0f b6 2c 25 00 00 00 00 48 8b
RSP: 0018:ffffc9000392f928 EFLAGS: 00010293
RAX: ffffffff812b42ab RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffff888026c65ac0 RSI: 00000000000001ff RDI: 0000000000000000
RBP: 0000000000000000 R08: ffff888069c000aa R09: 1ffff1100d380015
R10: dffffc0000000000 R11: ffffed100d380016 R12: 0000000000000008
R13: 00000000000001ff R14: 0000000000000000 R15: 0000000000000000
FS: 000055556a027500(0000) GS:ffff888125f29000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30363fff CR3: 0000000076c50000 CR4: 00000000003526f0
Call Trace:
<TASK>
seq_show+0x5bc/0x730 fs/proc/fd.c:68
seq_read_iter+0x4ef/0xe20 fs/seq_file.c:230
seq_read+0x369/0x480 fs/seq_file.c:162
vfs_read+0x200/0xa30 fs/read_write.c:570
ksys_read+0x145/0x250 fs/read_write.c:715
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f198c78efc9
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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffae1a3128 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007f198c9e5fa0 RCX: 00007f198c78efc9
RDX: 0000000000002020 RSI: 00002000000040c0 RDI: 0000000000000004
RBP: 00007f198c811f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f198c9e5fa0 R14: 00007f198c9e5fa0 R15: 0000000000000003
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__io_uring_show_fdinfo io_uring/fdinfo.c:103 [inline]
RIP: 0010:io_uring_show_fdinfo+0x371/0x1840 io_uring/fdinfo.c:255
Code: 0f 85 29 04 00 00 45 8b 36 44 89 f7 44 89 ee e8 a5 ec 94 00 45 39 ee 76 11 e8 db ea 94 00 45 89 fd 4c 8b 3c 24 e9 c9 03 00 00 <80> 3b 00 45 89 fd 0f 85 17 04 00 00 0f b6 2c 25 00 00 00 00 48 8b
RSP: 0018:ffffc9000392f928 EFLAGS: 00010293
RAX: ffffffff812b42ab RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffff888026c65ac0 RSI: 00000000000001ff RDI: 0000000000000000
RBP: 0000000000000000 R08: ffff888069c000aa R09: 1ffff1100d380015
R10: dffffc0000000000 R11: ffffed100d380016 R12: 0000000000000008
R13: 00000000000001ff R14: 0000000000000000 R15: 0000000000000000
FS: 000055556a027500(0000) GS:ffff888125f29000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30363fff CR3: 0000000076c50000 CR4: 00000000003526f0
----------------
Code disassembly (best guess):
0: 0f 85 29 04 00 00 jne 0x42f
6: 45 8b 36 mov (%r14),%r14d
9: 44 89 f7 mov %r14d,%edi
c: 44 89 ee mov %r13d,%esi
f: e8 a5 ec 94 00 call 0x94ecb9
14: 45 39 ee cmp %r13d,%r14d
17: 76 11 jbe 0x2a
19: e8 db ea 94 00 call 0x94eaf9
1e: 45 89 fd mov %r15d,%r13d
21: 4c 8b 3c 24 mov (%rsp),%r15
25: e9 c9 03 00 00 jmp 0x3f3
* 2a: 80 3b 00 cmpb $0x0,(%rbx) <-- trapping instruction
2d: 45 89 fd mov %r15d,%r13d
30: 0f 85 17 04 00 00 jne 0x44d
36: 0f b6 2c 25 00 00 00 movzbl 0x0,%ebp
3d: 00
3e: 48 rex.W
3f: 8b .byte 0x8b
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (4)
2025-10-23 21:21 [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (4) syzbot
@ 2025-10-23 21:34 ` Caleb Sander Mateos
2025-10-23 21:34 ` syzbot
2025-10-24 0:49 ` Jens Axboe
1 sibling, 1 reply; 5+ messages in thread
From: Caleb Sander Mateos @ 2025-10-23 21:34 UTC (permalink / raw)
To: syzbot; +Cc: axboe, io-uring, kbusch, linux-kernel, syzkaller-bugs
On Thu, Oct 23, 2025 at 2:21 PM syzbot
<syzbot+a77f64386b3e1b2ebb51@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: aaa9c3550b60 Add linux-next specific files for 20251022
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=11880c92580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c8b911aebadf6410
> dashboard link: https://syzkaller.appspot.com/bug?extid=a77f64386b3e1b2ebb51
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e73734580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=102f43e2580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/44f7af9b7ca1/disk-aaa9c355.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/9d09b0a9994d/vmlinux-aaa9c355.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/ae729ccb2c5c/bzImage-aaa9c355.xz
>
> The issue was bisected to:
>
> commit 31dc41afdef21f264364288a30013b538c46152e
> Author: Keith Busch <kbusch@kernel.org>
> Date: Thu Oct 16 18:09:38 2025 +0000
>
> io_uring: add support for IORING_SETUP_SQE_MIXED
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12eac614580000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=11eac614580000
> console output: https://syzkaller.appspot.com/x/log.txt?x=16eac614580000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a77f64386b3e1b2ebb51@syzkaller.appspotmail.com
> Fixes: 31dc41afdef2 ("io_uring: add support for IORING_SETUP_SQE_MIXED")
>
> Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
> KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
> CPU: 0 UID: 0 PID: 6032 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
> RIP: 0010:__io_uring_show_fdinfo io_uring/fdinfo.c:103 [inline]
> RIP: 0010:io_uring_show_fdinfo+0x371/0x1840 io_uring/fdinfo.c:255
> Code: 0f 85 29 04 00 00 45 8b 36 44 89 f7 44 89 ee e8 a5 ec 94 00 45 39 ee 76 11 e8 db ea 94 00 45 89 fd 4c 8b 3c 24 e9 c9 03 00 00 <80> 3b 00 45 89 fd 0f 85 17 04 00 00 0f b6 2c 25 00 00 00 00 48 8b
> RSP: 0018:ffffc9000392f928 EFLAGS: 00010293
> RAX: ffffffff812b42ab RBX: dffffc0000000000 RCX: 0000000000000000
> RDX: ffff888026c65ac0 RSI: 00000000000001ff RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffff888069c000aa R09: 1ffff1100d380015
> R10: dffffc0000000000 R11: ffffed100d380016 R12: 0000000000000008
> R13: 00000000000001ff R14: 0000000000000000 R15: 0000000000000000
> FS: 000055556a027500(0000) GS:ffff888125f29000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000001b30363fff CR3: 0000000076c50000 CR4: 00000000003526f0
> Call Trace:
> <TASK>
> seq_show+0x5bc/0x730 fs/proc/fd.c:68
> seq_read_iter+0x4ef/0xe20 fs/seq_file.c:230
> seq_read+0x369/0x480 fs/seq_file.c:162
> vfs_read+0x200/0xa30 fs/read_write.c:570
> ksys_read+0x145/0x250 fs/read_write.c:715
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f198c78efc9
> 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 a8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007fffae1a3128 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
> RAX: ffffffffffffffda RBX: 00007f198c9e5fa0 RCX: 00007f198c78efc9
> RDX: 0000000000002020 RSI: 00002000000040c0 RDI: 0000000000000004
> RBP: 00007f198c811f91 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007f198c9e5fa0 R14: 00007f198c9e5fa0 R15: 0000000000000003
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:__io_uring_show_fdinfo io_uring/fdinfo.c:103 [inline]
> RIP: 0010:io_uring_show_fdinfo+0x371/0x1840 io_uring/fdinfo.c:255
> Code: 0f 85 29 04 00 00 45 8b 36 44 89 f7 44 89 ee e8 a5 ec 94 00 45 39 ee 76 11 e8 db ea 94 00 45 89 fd 4c 8b 3c 24 e9 c9 03 00 00 <80> 3b 00 45 89 fd 0f 85 17 04 00 00 0f b6 2c 25 00 00 00 00 48 8b
> RSP: 0018:ffffc9000392f928 EFLAGS: 00010293
> RAX: ffffffff812b42ab RBX: dffffc0000000000 RCX: 0000000000000000
> RDX: ffff888026c65ac0 RSI: 00000000000001ff RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffff888069c000aa R09: 1ffff1100d380015
> R10: dffffc0000000000 R11: ffffed100d380016 R12: 0000000000000008
> R13: 00000000000001ff R14: 0000000000000000 R15: 0000000000000000
> FS: 000055556a027500(0000) GS:ffff888125f29000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000001b30363fff CR3: 0000000076c50000 CR4: 00000000003526f0
> ----------------
> Code disassembly (best guess):
> 0: 0f 85 29 04 00 00 jne 0x42f
> 6: 45 8b 36 mov (%r14),%r14d
> 9: 44 89 f7 mov %r14d,%edi
> c: 44 89 ee mov %r13d,%esi
> f: e8 a5 ec 94 00 call 0x94ecb9
> 14: 45 39 ee cmp %r13d,%r14d
> 17: 76 11 jbe 0x2a
> 19: e8 db ea 94 00 call 0x94eaf9
> 1e: 45 89 fd mov %r15d,%r13d
> 21: 4c 8b 3c 24 mov (%rsp),%r15
> 25: e9 c9 03 00 00 jmp 0x3f3
> * 2a: 80 3b 00 cmpb $0x0,(%rbx) <-- trapping instruction
> 2d: 45 89 fd mov %r15d,%r13d
> 30: 0f 85 17 04 00 00 jne 0x44d
> 36: 0f b6 2c 25 00 00 00 movzbl 0x0,%ebp
> 3d: 00
> 3e: 48 rex.W
> 3f: 8b .byte 0x8b
>
>
> ---
> 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 syzkaller@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
> If the report is already addressed, let syzbot know by replying with:
> #syz fix: exact-commit-title
>
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before testing.
>
> 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
#syz dup: [syzbot] [io-uring?] general protection fault in
io_uring_show_fdinfo (3)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (4)
2025-10-23 21:34 ` Caleb Sander Mateos
@ 2025-10-23 21:34 ` syzbot
0 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2025-10-23 21:34 UTC (permalink / raw)
To: csander; +Cc: axboe, csander, io-uring, kbusch, linux-kernel, syzkaller-bugs
> On Thu, Oct 23, 2025 at 2:21 PM syzbot
> <syzbot+a77f64386b3e1b2ebb51@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: aaa9c3550b60 Add linux-next specific files for 20251022
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=11880c92580000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=c8b911aebadf6410
>> dashboard link: https://syzkaller.appspot.com/bug?extid=a77f64386b3e1b2ebb51
>> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e73734580000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=102f43e2580000
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/44f7af9b7ca1/disk-aaa9c355.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/9d09b0a9994d/vmlinux-aaa9c355.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/ae729ccb2c5c/bzImage-aaa9c355.xz
>>
>> The issue was bisected to:
>>
>> commit 31dc41afdef21f264364288a30013b538c46152e
>> Author: Keith Busch <kbusch@kernel.org>
>> Date: Thu Oct 16 18:09:38 2025 +0000
>>
>> io_uring: add support for IORING_SETUP_SQE_MIXED
>>
>> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12eac614580000
>> final oops: https://syzkaller.appspot.com/x/report.txt?x=11eac614580000
>> console output: https://syzkaller.appspot.com/x/log.txt?x=16eac614580000
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+a77f64386b3e1b2ebb51@syzkaller.appspotmail.com
>> Fixes: 31dc41afdef2 ("io_uring: add support for IORING_SETUP_SQE_MIXED")
>>
>> Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
>> KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
>> CPU: 0 UID: 0 PID: 6032 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
>> RIP: 0010:__io_uring_show_fdinfo io_uring/fdinfo.c:103 [inline]
>> RIP: 0010:io_uring_show_fdinfo+0x371/0x1840 io_uring/fdinfo.c:255
>> Code: 0f 85 29 04 00 00 45 8b 36 44 89 f7 44 89 ee e8 a5 ec 94 00 45 39 ee 76 11 e8 db ea 94 00 45 89 fd 4c 8b 3c 24 e9 c9 03 00 00 <80> 3b 00 45 89 fd 0f 85 17 04 00 00 0f b6 2c 25 00 00 00 00 48 8b
>> RSP: 0018:ffffc9000392f928 EFLAGS: 00010293
>> RAX: ffffffff812b42ab RBX: dffffc0000000000 RCX: 0000000000000000
>> RDX: ffff888026c65ac0 RSI: 00000000000001ff RDI: 0000000000000000
>> RBP: 0000000000000000 R08: ffff888069c000aa R09: 1ffff1100d380015
>> R10: dffffc0000000000 R11: ffffed100d380016 R12: 0000000000000008
>> R13: 00000000000001ff R14: 0000000000000000 R15: 0000000000000000
>> FS: 000055556a027500(0000) GS:ffff888125f29000(0000) knlGS:0000000000000000
>> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: 0000001b30363fff CR3: 0000000076c50000 CR4: 00000000003526f0
>> Call Trace:
>> <TASK>
>> seq_show+0x5bc/0x730 fs/proc/fd.c:68
>> seq_read_iter+0x4ef/0xe20 fs/seq_file.c:230
>> seq_read+0x369/0x480 fs/seq_file.c:162
>> vfs_read+0x200/0xa30 fs/read_write.c:570
>> ksys_read+0x145/0x250 fs/read_write.c:715
>> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>> do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
>> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>> RIP: 0033:0x7f198c78efc9
>> 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 a8 ff ff ff f7 d8 64 89 01 48
>> RSP: 002b:00007fffae1a3128 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
>> RAX: ffffffffffffffda RBX: 00007f198c9e5fa0 RCX: 00007f198c78efc9
>> RDX: 0000000000002020 RSI: 00002000000040c0 RDI: 0000000000000004
>> RBP: 00007f198c811f91 R08: 0000000000000000 R09: 0000000000000000
>> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
>> R13: 00007f198c9e5fa0 R14: 00007f198c9e5fa0 R15: 0000000000000003
>> </TASK>
>> Modules linked in:
>> ---[ end trace 0000000000000000 ]---
>> RIP: 0010:__io_uring_show_fdinfo io_uring/fdinfo.c:103 [inline]
>> RIP: 0010:io_uring_show_fdinfo+0x371/0x1840 io_uring/fdinfo.c:255
>> Code: 0f 85 29 04 00 00 45 8b 36 44 89 f7 44 89 ee e8 a5 ec 94 00 45 39 ee 76 11 e8 db ea 94 00 45 89 fd 4c 8b 3c 24 e9 c9 03 00 00 <80> 3b 00 45 89 fd 0f 85 17 04 00 00 0f b6 2c 25 00 00 00 00 48 8b
>> RSP: 0018:ffffc9000392f928 EFLAGS: 00010293
>> RAX: ffffffff812b42ab RBX: dffffc0000000000 RCX: 0000000000000000
>> RDX: ffff888026c65ac0 RSI: 00000000000001ff RDI: 0000000000000000
>> RBP: 0000000000000000 R08: ffff888069c000aa R09: 1ffff1100d380015
>> R10: dffffc0000000000 R11: ffffed100d380016 R12: 0000000000000008
>> R13: 00000000000001ff R14: 0000000000000000 R15: 0000000000000000
>> FS: 000055556a027500(0000) GS:ffff888125f29000(0000) knlGS:0000000000000000
>> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: 0000001b30363fff CR3: 0000000076c50000 CR4: 00000000003526f0
>> ----------------
>> Code disassembly (best guess):
>> 0: 0f 85 29 04 00 00 jne 0x42f
>> 6: 45 8b 36 mov (%r14),%r14d
>> 9: 44 89 f7 mov %r14d,%edi
>> c: 44 89 ee mov %r13d,%esi
>> f: e8 a5 ec 94 00 call 0x94ecb9
>> 14: 45 39 ee cmp %r13d,%r14d
>> 17: 76 11 jbe 0x2a
>> 19: e8 db ea 94 00 call 0x94eaf9
>> 1e: 45 89 fd mov %r15d,%r13d
>> 21: 4c 8b 3c 24 mov (%rsp),%r15
>> 25: e9 c9 03 00 00 jmp 0x3f3
>> * 2a: 80 3b 00 cmpb $0x0,(%rbx) <-- trapping instruction
>> 2d: 45 89 fd mov %r15d,%r13d
>> 30: 0f 85 17 04 00 00 jne 0x44d
>> 36: 0f b6 2c 25 00 00 00 movzbl 0x0,%ebp
>> 3d: 00
>> 3e: 48 rex.W
>> 3f: 8b .byte 0x8b
>>
>>
>> ---
>> 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 syzkaller@googlegroups.com.
>>
>> syzbot will keep track of this issue. See:
>> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
>> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>>
>> If the report is already addressed, let syzbot know by replying with:
>> #syz fix: exact-commit-title
>>
>> If you want syzbot to run the reproducer, reply with:
>> #syz test: git://repo/address.git branch-or-commit-hash
>> If you attach or paste a git patch, syzbot will apply it before testing.
>>
>> 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
>
> #syz dup: [syzbot] [io-uring?] general protection fault in
can't find the dup bug
> io_uring_show_fdinfo (3)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (4)
[not found] <CADUfDZpnsv1--j02NW+d9woX1VvR7q3Ed0W_hO-GZmkCVfSH7g@mail.gmail.com>
@ 2025-10-23 21:35 ` syzbot
0 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2025-10-23 21:35 UTC (permalink / raw)
To: csander; +Cc: axboe, csander, io-uring, kbusch, linux-kernel, syzkaller-bugs
> On Thu, Oct 23, 2025 at 2:34 PM syzbot <
> syzbot+a77f64386b3e1b2ebb51@syzkaller.appspotmail.com> wrote:
>>
>> > On Thu, Oct 23, 2025 at 2:21 PM syzbot
>> > <syzbot+a77f64386b3e1b2ebb51@syzkaller.appspotmail.com> wrote:
>> >>
>> >> Hello,
>> >>
>> >> syzbot found the following issue on:
>> >>
>> >> HEAD commit: aaa9c3550b60 Add linux-next specific files for 20251022
>> >> git tree: linux-next
>> >> console output:
> https://syzkaller.appspot.com/x/log.txt?x=11880c92580000
>> >> kernel config:
> https://syzkaller.appspot.com/x/.config?x=c8b911aebadf6410
>> >> dashboard link:
> https://syzkaller.appspot.com/bug?extid=a77f64386b3e1b2ebb51
>> >> compiler: Debian clang version 20.1.8
> (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
>> >> syz repro:
> https://syzkaller.appspot.com/x/repro.syz?x=12e73734580000
>> >> C reproducer:
> https://syzkaller.appspot.com/x/repro.c?x=102f43e2580000
>> >>
>> >> Downloadable assets:
>> >> disk image:
> https://storage.googleapis.com/syzbot-assets/44f7af9b7ca1/disk-aaa9c355.raw.xz
>> >> vmlinux:
> https://storage.googleapis.com/syzbot-assets/9d09b0a9994d/vmlinux-aaa9c355.xz
>> >> kernel image:
> https://storage.googleapis.com/syzbot-assets/ae729ccb2c5c/bzImage-aaa9c355.xz
>> >>
>> >> The issue was bisected to:
>> >>
>> >> commit 31dc41afdef21f264364288a30013b538c46152e
>> >> Author: Keith Busch <kbusch@kernel.org>
>> >> Date: Thu Oct 16 18:09:38 2025 +0000
>> >>
>> >> io_uring: add support for IORING_SETUP_SQE_MIXED
>> >>
>> >> bisection log:
> https://syzkaller.appspot.com/x/bisect.txt?x=12eac614580000
>> >> final oops:
> https://syzkaller.appspot.com/x/report.txt?x=11eac614580000
>> >> console output:
> https://syzkaller.appspot.com/x/log.txt?x=16eac614580000
>> >>
>> >> IMPORTANT: if you fix the issue, please add the following tag to the
> commit:
>> >> Reported-by: syzbot+a77f64386b3e1b2ebb51@syzkaller.appspotmail.com
>> >> Fixes: 31dc41afdef2 ("io_uring: add support for
> IORING_SETUP_SQE_MIXED")
>> >>
>> >> Oops: general protection fault, probably for non-canonical address
> 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
>> >> KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
>> >> CPU: 0 UID: 0 PID: 6032 Comm: syz.0.17 Not tainted syzkaller #0
> PREEMPT(full)
>> >> Hardware name: Google Google Compute Engine/Google Compute Engine,
> BIOS Google 10/02/2025
>> >> RIP: 0010:__io_uring_show_fdinfo io_uring/fdinfo.c:103 [inline]
>> >> RIP: 0010:io_uring_show_fdinfo+0x371/0x1840 io_uring/fdinfo.c:255
>> >> Code: 0f 85 29 04 00 00 45 8b 36 44 89 f7 44 89 ee e8 a5 ec 94 00 45
> 39 ee 76 11 e8 db ea 94 00 45 89 fd 4c 8b 3c 24 e9 c9 03 00 00 <80> 3b 00
> 45 89 fd 0f 85 17 04 00 00 0f b6 2c 25 00 00 00 00 48 8b
>> >> RSP: 0018:ffffc9000392f928 EFLAGS: 00010293
>> >> RAX: ffffffff812b42ab RBX: dffffc0000000000 RCX: 0000000000000000
>> >> RDX: ffff888026c65ac0 RSI: 00000000000001ff RDI: 0000000000000000
>> >> RBP: 0000000000000000 R08: ffff888069c000aa R09: 1ffff1100d380015
>> >> R10: dffffc0000000000 R11: ffffed100d380016 R12: 0000000000000008
>> >> R13: 00000000000001ff R14: 0000000000000000 R15: 0000000000000000
>> >> FS: 000055556a027500(0000) GS:ffff888125f29000(0000)
> knlGS:0000000000000000
>> >> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> >> CR2: 0000001b30363fff CR3: 0000000076c50000 CR4: 00000000003526f0
>> >> Call Trace:
>> >> <TASK>
>> >> seq_show+0x5bc/0x730 fs/proc/fd.c:68
>> >> seq_read_iter+0x4ef/0xe20 fs/seq_file.c:230
>> >> seq_read+0x369/0x480 fs/seq_file.c:162
>> >> vfs_read+0x200/0xa30 fs/read_write.c:570
>> >> ksys_read+0x145/0x250 fs/read_write.c:715
>> >> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>> >> do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
>> >> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>> >> RIP: 0033:0x7f198c78efc9
>> >> 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 a8 ff ff ff f7 d8 64 89 01 48
>> >> RSP: 002b:00007fffae1a3128 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
>> >> RAX: ffffffffffffffda RBX: 00007f198c9e5fa0 RCX: 00007f198c78efc9
>> >> RDX: 0000000000002020 RSI: 00002000000040c0 RDI: 0000000000000004
>> >> RBP: 00007f198c811f91 R08: 0000000000000000 R09: 0000000000000000
>> >> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
>> >> R13: 00007f198c9e5fa0 R14: 00007f198c9e5fa0 R15: 0000000000000003
>> >> </TASK>
>> >> Modules linked in:
>> >> ---[ end trace 0000000000000000 ]---
>> >> RIP: 0010:__io_uring_show_fdinfo io_uring/fdinfo.c:103 [inline]
>> >> RIP: 0010:io_uring_show_fdinfo+0x371/0x1840 io_uring/fdinfo.c:255
>> >> Code: 0f 85 29 04 00 00 45 8b 36 44 89 f7 44 89 ee e8 a5 ec 94 00 45
> 39 ee 76 11 e8 db ea 94 00 45 89 fd 4c 8b 3c 24 e9 c9 03 00 00 <80> 3b 00
> 45 89 fd 0f 85 17 04 00 00 0f b6 2c 25 00 00 00 00 48 8b
>> >> RSP: 0018:ffffc9000392f928 EFLAGS: 00010293
>> >> RAX: ffffffff812b42ab RBX: dffffc0000000000 RCX: 0000000000000000
>> >> RDX: ffff888026c65ac0 RSI: 00000000000001ff RDI: 0000000000000000
>> >> RBP: 0000000000000000 R08: ffff888069c000aa R09: 1ffff1100d380015
>> >> R10: dffffc0000000000 R11: ffffed100d380016 R12: 0000000000000008
>> >> R13: 00000000000001ff R14: 0000000000000000 R15: 0000000000000000
>> >> FS: 000055556a027500(0000) GS:ffff888125f29000(0000)
> knlGS:0000000000000000
>> >> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> >> CR2: 0000001b30363fff CR3: 0000000076c50000 CR4: 00000000003526f0
>> >> ----------------
>> >> Code disassembly (best guess):
>> >> 0: 0f 85 29 04 00 00 jne 0x42f
>> >> 6: 45 8b 36 mov (%r14),%r14d
>> >> 9: 44 89 f7 mov %r14d,%edi
>> >> c: 44 89 ee mov %r13d,%esi
>> >> f: e8 a5 ec 94 00 call 0x94ecb9
>> >> 14: 45 39 ee cmp %r13d,%r14d
>> >> 17: 76 11 jbe 0x2a
>> >> 19: e8 db ea 94 00 call 0x94eaf9
>> >> 1e: 45 89 fd mov %r15d,%r13d
>> >> 21: 4c 8b 3c 24 mov (%rsp),%r15
>> >> 25: e9 c9 03 00 00 jmp 0x3f3
>> >> * 2a: 80 3b 00 cmpb $0x0,(%rbx) <-- trapping
> instruction
>> >> 2d: 45 89 fd mov %r15d,%r13d
>> >> 30: 0f 85 17 04 00 00 jne 0x44d
>> >> 36: 0f b6 2c 25 00 00 00 movzbl 0x0,%ebp
>> >> 3d: 00
>> >> 3e: 48 rex.W
>> >> 3f: 8b .byte 0x8b
>> >>
>> >>
>> >> ---
>> >> 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 syzkaller@googlegroups.com.
>> >>
>> >> syzbot will keep track of this issue. See:
>> >> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
>> >> For information about bisection process see:
> https://goo.gl/tpsmEJ#bisection
>> >>
>> >> If the report is already addressed, let syzbot know by replying with:
>> >> #syz fix: exact-commit-title
>> >>
>> >> If you want syzbot to run the reproducer, reply with:
>> >> #syz test: git://repo/address.git branch-or-commit-hash
>> >> If you attach or paste a git patch, syzbot will apply it before
> testing.
>> >>
>> >> 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
>> >
>> > #syz dup: [syzbot] [io-uring?] general protection fault in
>>
>> can't find the dup bug
>>
>> > io_uring_show_fdinfo (3)
>
> #syz dup: [syzbot] [io-uring?] general protection fault in
can't find the dup bug
> io_uring_show_fdinfo (3)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (4)
2025-10-23 21:21 [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (4) syzbot
2025-10-23 21:34 ` Caleb Sander Mateos
@ 2025-10-24 0:49 ` Jens Axboe
1 sibling, 0 replies; 5+ messages in thread
From: Jens Axboe @ 2025-10-24 0:49 UTC (permalink / raw)
To: syzbot, io-uring, kbusch, linux-kernel, syzkaller-bugs
#syz invalid
--
Jens Axboe
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2025-10-24 0:49 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-10-23 21:21 [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (4) syzbot
2025-10-23 21:34 ` Caleb Sander Mateos
2025-10-23 21:34 ` syzbot
2025-10-24 0:49 ` Jens Axboe
[not found] <CADUfDZpnsv1--j02NW+d9woX1VvR7q3Ed0W_hO-GZmkCVfSH7g@mail.gmail.com>
2025-10-23 21:35 ` syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox