From: syzbot <syzbot+de3d7f9bcc9212f3fae1@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [trace?] WARNING in ring_buffer_map_get_reader (3)
Date: Mon, 07 Sep 2026 10:57:25 -0700 [thread overview]
Message-ID: <6a9efb05.f81106d8.4d30e.0002.GAE@google.com> (raw)
In-Reply-To: <6a9dc9e7.87c06881.102b7.0007.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: df2908090cda Linux 7.3-rc2
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1216caf9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=de3d7f9bcc9212f3fae1
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1616caf9580000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+de3d7f9bcc9212f3fae1@syzkaller.appspotmail.com
Ring buffer [0] commit overrun lost 3 events at timestamp:71798603963
------------[ cut here ]------------
!reader
WARNING: kernel/trace/ring_buffer.c:7998 at ring_buffer_map_get_reader+0x5f3/0x930 kernel/trace/ring_buffer.c:7998, CPU#1: syz-executor388/6024
Modules linked in:
CPU: 1 UID: 0 PID: 6024 Comm: syz-executor388 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:ring_buffer_map_get_reader+0x5f3/0x930 kernel/trace/ring_buffer.c:7998
Code: ff 48 89 df e8 be 22 fe ff 48 89 c5 e8 a6 88 fb ff 48 85 ed 0f 85 9f fc ff ff 4c 8b 74 24 58 4c 8b 7c 24 60 e8 8e 88 fb ff 90 <0f> 0b 90 e8 85 88 fb ff 49 8d bf d0 01 00 00 48 b8 00 00 00 00 00
RSP: 0018:ffffc90003977d98 EFLAGS: 00010093
RAX: 0000000000000000 RBX: ffff88801c0e5000 RCX: 0000000000000001
RDX: ffff8880333d4b00 RSI: ffffffff82108882 RDI: ffff8880333d4b00
RBP: 0000000000000000 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000000 R11: ffff88801c0e50b0 R12: ffff88801c0e50b8
R13: dffffc0000000000 R14: ffff88801c0e5198 R15: ffff88801c0ab800
FS: 00007f337024b6c0(0000) GS:ffff8880d5c5d000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000559c2c45caa0 CR3: 000000003dec3000 CR4: 0000000000352ef0
Call Trace:
<TASK>
tracing_buffers_ioctl+0x2e6/0x3d0 kernel/trace/trace.c:7381
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f3370a8136b
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
RSP: 002b:00007f337024b130 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f337024bcdc RCX: 00007f3370a8136b
RDX: 0000000000000000 RSI: 0000000000005220 RDI: 0000000000000004
RBP: 0000000000000021 R08: 0000000000000000 R09: 00007f337024b6c0
R10: 0000000000000008 R11: 0000000000000246 R12: ffffffffffffffd0
R13: 0000000000000000 R14: 00007ffc1cde9710 R15: 00007ffc1cde97f8
</TASK>
---
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.
next prev parent reply other threads:[~2026-09-07 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 20:15 syzbot
2026-09-07 17:57 ` syzbot [this message]
2026-09-10 11:48 ` Forwarded: Re: test patch syzbot
[not found] <20260910114832.20899-1-tahasami8@gmail.com>
2026-09-10 12:02 ` [syzbot] [trace?] WARNING in ring_buffer_map_get_reader (3) syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a9efb05.f81106d8.4d30e.0002.GAE@google.com \
--to=syzbot+de3d7f9bcc9212f3fae1@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®