From: Steven Rostedt <rostedt@goodmis.org>
To: Ankit Khushwaha <ankitkhushwaha.linux@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
david.hunter.linux@gmail.com, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
syzbot+ddc001b92c083dbf2b97@syzkaller.appspotmail.com
Subject: Re: [PATCH] ring buffer: propagate __rb_map_vma return value to caller
Date: Wed, 8 Oct 2025 12:11:10 -0400 [thread overview]
Message-ID: <20251008121110.4e7c3671@gandalf.local.home> (raw)
In-Reply-To: <20251007171256.20884-1-ankitkhushwaha.linux@gmail.com>
On Tue, 7 Oct 2025 22:42:56 +0530
Ankit Khushwaha <ankitkhushwaha.linux@gmail.com> wrote:
Note, tracing subsystem expects the subject to start with a capital letter:
ring buffer: Propagate __rb_map_vma return value to caller
> The return value from `__rb_map_vma()`, which rejects writable or
> executable mappings (VM_WRITE, VM_EXEC, or !VM_MAYSHARE), was being
> ignored. As a result the caller of `__rb_map_vma` always returned 0
> even when the mapping had actually failed, allowing it to proceed
> with an invalid VMA.
>
> Reported-by: syzbot+ddc001b92c083dbf2b97@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?id=194151be8eaebd826005329b2e123aecae714bdb
> Signed-off-by: Ankit Khushwaha <ankitkhushwaha.linux@gmail.com>
> ---
>
> #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 4ff71af020ae
>
> ---
> kernel/trace/ring_buffer.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 43460949ad3f..4efb90364f48 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -7271,6 +7271,8 @@ int ring_buffer_map(struct trace_buffer *buffer, int cpu,
> cpu_buffer->subbuf_ids = NULL;
> rb_free_meta_page(cpu_buffer);
> atomic_dec(&cpu_buffer->resize_disabled);
> + /* VM failed to be mapped */
No need to add the comment. It's obvious what happened.
> + return err;
Don't return here.
> }
>
> return 0;
Change this to:
return err;
as after that if statement, err will be 0 on success or the value you want
to return.
-- Steve
prev parent reply other threads:[~2025-10-08 16:09 UTC|newest]
Thread overview: 3+ 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] [trace?] WARNING in tracing_buffers_mmap_close syzbot
2025-10-08 16:11 ` Steven Rostedt [this message]
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=20251008121110.4e7c3671@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=skhan@linuxfoundation.org \
--cc=syzbot+ddc001b92c083dbf2b97@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).