[v6.1] WARNING in ring_buffer_peek

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dc5c83b7f5f8 Linux 6.1.178
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1068e449580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=c560c412639853d85b5d
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a9aa438e39c2/disk-dc5c83b7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a7b5afd2e170/vmlinux-dc5c83b7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c7673d370fb/bzImage-dc5c83b7.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 6351 at kernel/trace/ring_buffer.c:4571 arch_atomic_inc include/linux/instrumented.h:102 [inline]
WARNING: CPU: 1 PID: 6351 at kernel/trace/ring_buffer.c:4571 atomic_inc include/linux/atomic/atomic-instrumented.h:191 [inline]
WARNING: CPU: 1 PID: 6351 at kernel/trace/ring_buffer.c:4571 rb_get_reader_page+0xabf/0xcd0 kernel/trace/ring_buffer.c:4570
Modules linked in:
CPU: 1 PID: 6351 Comm: syz.1.645 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:rb_get_reader_page+0xabf/0xcd0 kernel/trace/ring_buffer.c:4570
Code: 48 c1 e8 03 42 80 3c 38 00 74 08 4c 89 e7 e8 78 37 4e 00 4d 8b 3c 24 49 8d 7f 08 be 04 00 00 00 e8 06 39 4e 00 f0 41 ff 47 08 <0f> 0b 49 bf 00 00 00 00 00 fc ff df 4c 8b 6c 24 30 48 83 7c 24 18
RSP: 0018:ffffc900033977e0 EFLAGS: 00010002
RAX: 1ffff11002e8f101 RBX: 1ffff11002e8e876 RCX: ffffffff8185294a
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffff888017470408
RBP: ffffc90003397970 R08: ffff88801747040b R09: 1ffff11002e8e081
R10: dffffc0000000000 R11: ffffed1002e8e082 R12: ffff888017478810
R13: 0000000000000104 R14: 1ffff11002e8e873 R15: ffff888017470400
FS: 00007fe396cad6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcfcf7556b8 CR3: 0000000077da2000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
rb_buffer_peek+0x5e/0x940 kernel/trace/ring_buffer.c:4784
ring_buffer_peek+0x1f8/0x440 kernel/trace/ring_buffer.c:4986
peek_next_entry+0x113/0x1c0 kernel/trace/trace.c:3596
__find_next_entry+0x547/0x6c0 kernel/trace/trace.c:3628
trace_find_next_entry_inc kernel/trace/trace.c:4021 [inline]
tracing_read_pipe+0x3bd/0xb10 kernel/trace/trace.c:6882
vfs_read+0x2db/0x960 fs/read_write.c:468
ksys_read+0x14d/0x260 fs/read_write.c:613
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe395d9de99
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe396cad028 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007fe396025fa0 RCX: 00007fe395d9de99
RDX: 0000000000000064 RSI: 0000200000000b00 RDI: 0000000000000004
RBP: 00007fe395e33eaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fe396026038 R14: 00007fe396025fa0 R15: 00007ffc8dec3e58
</TASK>


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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6e2fd6534337 Linux 5.15.213
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12f0fa49580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link: https://syzkaller.appspot.com/bug?extid=fcaa1d3c63ce2e755ff8

compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/d7b46606b13d/disk-6e2fd653.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/da120fdeb081/vmlinux-6e2fd653.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c2643457e3f/bzImage-6e2fd653.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+fcaa1d...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 8049 at kernel/trace/ring_buffer.c:4528 arch_atomic_inc include/linux/instrumented.h:101 [inline]
WARNING: CPU: 1 PID: 8049 at kernel/trace/ring_buffer.c:4528 atomic_inc include/linux/atomic/atomic-instrumented.h:182 [inline]
WARNING: CPU: 1 PID: 8049 at kernel/trace/ring_buffer.c:4528 rb_get_reader_page+0xac0/0xcd0 kernel/trace/ring_buffer.c:4527
Modules linked in:
CPU: 1 PID: 8049 Comm: syz.7.1122 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:rb_get_reader_page+0xac0/0xcd0 kernel/trace/ring_buffer.c:4527
Code: 48 c1 e8 03 42 80 3c 38 00 74 08 4c 89 e7 e8 87 4b 42 00 4d 8b 3c 24 49 8d 7f 08 be 04 00 00 00 e8 15 4d 42 00 f0 41 ff 47 08 <0f> 0b 49 bf 00 00 00 00 00 fc ff df 4c 8b 6c 24 30 48 83 7c 24 18
RSP: 0018:ffffc900034277c0 EFLAGS: 00010002
RAX: 1ffff11002db9f01 RBX: 1ffff11027fcb9d6 RCX: ffffffff817bd3fb
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffff888016c70408
RBP: ffffc90003427960 R08: ffff888016c7040b R09: 1ffff11002d8e081
R10: dffffc0000000000 R11: ffffed1002d8e082 R12: ffff888016dcf810
R13: 0000000000000090 R14: 1ffff11027fcb9d3 R15: ffff888016c70400
FS: 00007fd2150766c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 000000110c390d2e CR3: 0000000079215000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>

rb_buffer_peek+0x5c/0x780 kernel/trace/ring_buffer.c:4741
ring_buffer_peek+0x1de/0x400 kernel/trace/ring_buffer.c:4941
peek_next_entry kernel/trace/trace.c:3572 [inline]
__find_next_entry+0x350/0x6b0 kernel/trace/trace.c:3616
trace_find_next_entry_inc kernel/trace/trace.c:3997 [inline]
tracing_read_pipe+0x3b1/0xae0 kernel/trace/trace.c:6858
vfs_read+0x2ff/0xd50 fs/read_write.c:483
ksys_read+0x153/0x260 fs/read_write.c:623
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fd216e1e019

Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007fd215076028 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007fd2170a5fa0 RCX: 00007fd216e1e019
RDX: 0000000000002000 RSI: 0000200000004000 RDI: 0000000000000003
RBP: 00007fd216eb500c R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000

R13: 00007fd2170a6038 R14: 00007fd2170a5fa0 R15: 00007ffc0aa26ed8