From: syzbot <syzbot+ddc001b92c083dbf2b97@syzkaller.appspotmail.com>
To: ankitkhushwaha.linux@gmail.com, david.hunter.linux@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
rostedt@goodmis.org, skhan@linuxfoundation.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [trace?] WARNING in tracing_buffers_mmap_close
Date: Tue, 07 Oct 2025 10:45:02 -0700 [thread overview]
Message-ID: <68e5519e.a00a0220.298cc0.0482.GAE@google.com> (raw)
In-Reply-To: <20251007171256.20884-1-ankitkhushwaha.linux@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+ddc001b92c083dbf2b97@syzkaller.appspotmail.com
Tested-by: syzbot+ddc001b92c083dbf2b97@syzkaller.appspotmail.com
Tested on:
commit: 4ff71af0 Merge tag 'net-6.17-rc8' of git://git.kernel...
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17676892580000
kernel config: https://syzkaller.appspot.com/x/.config?x=595e5938a1dd5b4e
dashboard link: https://syzkaller.appspot.com/bug?extid=ddc001b92c083dbf2b97
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1249d1e2580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-07 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 17:12 [PATCH] ring buffer: propagate __rb_map_vma return value to caller Ankit Khushwaha
2025-10-07 17:45 ` syzbot [this message]
2025-10-08 16:11 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2024-12-15 20:34 [syzbot] [trace?] WARNING in tracing_buffers_mmap_close 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=68e5519e.a00a0220.298cc0.0482.GAE@google.com \
--to=syzbot+ddc001b92c083dbf2b97@syzkaller.appspotmail.com \
--cc=ankitkhushwaha.linux@gmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--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=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.