From: Steven Rostedt <rostedt@goodmis.org>
To: Petr Pavlu <petr.pavlu@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] ring-buffer: Have the buffer update counter be atomic
Date: Fri, 11 Oct 2024 12:53:46 -0400 [thread overview]
Message-ID: <20241011125346.5edffba6@gandalf.local.home> (raw)
In-Reply-To: <84179edb-dba1-42fd-88a9-70d05d8915ec@suse.com>
On Fri, 11 Oct 2024 17:20:12 +0200
Petr Pavlu <petr.pavlu@suse.com> wrote:
> >From 359f5aa523bc27ca8600b4efae471eefc0514ce0 Mon Sep 17 00:00:00 2001
> From: Petr Pavlu <petr.pavlu@suse.com>
> Date: Tue, 16 Jul 2024 11:35:00 +0200
> Subject: [PATCH] ring-buffer: Fix reader locking when changing the sub buffer
> order
>
> The function ring_buffer_subbuf_order_set() updates each
> ring_buffer_per_cpu and installs new sub buffers that match the requested
> page order. This operation may be invoked concurrently with readers that
> rely on some of the modified data, such as the head bit (RB_PAGE_HEAD), or
> the ring_buffer_per_cpu.pages and reader_page pointers. However, no
> exclusive access is acquired by ring_buffer_subbuf_order_set(). Modyfing
> the mentioned data while a reader also operates on them can then result in
> incorrect memory access and various crashes.
>
> Fix the problem by taking the reader_lock when updating a specific
> ring_buffer_per_cpu in ring_buffer_subbuf_order_set().
>
> Fixes: 8e7b58c27b3c ("ring-buffer: Just update the subbuffers when changing their allocation order")
> Signed-off-by: Petr Pavlu <petr.pavlu@suse.com>
> ---
> kernel/trace/ring_buffer.c | 41 ++++++++++++++++++++++++--------------
> 1 file changed, 26 insertions(+), 15 deletions(-)
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 4c24191fa47d..d324f4f9ab9d 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -6773,36 +6773,38 @@ int ring_buffer_subbuf_order_set(struct trace_buffer *buffer, int order)
> }
>
> for_each_buffer_cpu(buffer, cpu) {
> + struct buffer_data_page *old_free_data_page;
> + struct list_head old_pages;
> + unsigned long flags;
>
> if (!cpumask_test_cpu(cpu, buffer->cpumask))
> continue;
>
> cpu_buffer = buffer->buffers[cpu];
>
> + raw_spin_lock_irqsave(&cpu_buffer->reader_lock, flags);
> +
> /* Clear the head bit to make the link list normal to read */
> rb_head_page_deactivate(cpu_buffer);
>
> - /* Now walk the list and free all the old sub buffers */
> - list_for_each_entry_safe(bpage, tmp, cpu_buffer->pages, list) {
> - list_del_init(&bpage->list);
> - free_buffer_page(bpage);
> - }
> - /* The above loop stopped an the last page needing to be freed */
> - bpage = list_entry(cpu_buffer->pages, struct buffer_page, list);
> - free_buffer_page(bpage);
> -
> - /* Free the current reader page */
> - free_buffer_page(cpu_buffer->reader_page);
> + /*
> + * Collect buffers from the cpu_buffer pages list and the
> + * reader_page on old_pages, so they can be freed later when not
> + * under a spinlock. The pages list is a linked list with no
> + * head, adding old_pages turns it into a regular list with
> + * old_pages being the head.
> + */
> + list_add(&old_pages, cpu_buffer->pages);
> + list_add(&cpu_buffer->reader_page->list, &old_pages);
>
> /* One page was allocated for the reader page */
> cpu_buffer->reader_page = list_entry(cpu_buffer->new_pages.next,
> struct buffer_page, list);
> list_del_init(&cpu_buffer->reader_page->list);
>
> - /* The cpu_buffer pages are a link list with no head */
> + /* Install the new pages, remove the head from the list */
> cpu_buffer->pages = cpu_buffer->new_pages.next;
> - cpu_buffer->new_pages.next->prev = cpu_buffer->new_pages.prev;
> - cpu_buffer->new_pages.prev->next = cpu_buffer->new_pages.next;
> + list_del(&cpu_buffer->new_pages);
Heh, not sure why I didn't just use list_del() on the head itself instead
of open coding it. But anyway, it should be list_del_init(), as I will
likely remove the initialization of new_pages and have it always be
initialized. I rather have it clean than pointing to something unknown.
Care to send this as a real patch?
We can look at any other locking issues here separately, but this should be
fixed now.
-- Steve
> cpu_buffer->cnt++;
>
> /* Clear the new_pages list */
> @@ -6815,11 +6817,20 @@ int ring_buffer_subbuf_order_set(struct trace_buffer *buffer, int order)
> cpu_buffer->nr_pages = cpu_buffer->nr_pages_to_update;
> cpu_buffer->nr_pages_to_update = 0;
>
> - free_pages((unsigned long)cpu_buffer->free_page, old_order);
> + old_free_data_page = cpu_buffer->free_page;
> cpu_buffer->free_page = NULL;
>
> rb_head_page_activate(cpu_buffer);
>
> + raw_spin_unlock_irqrestore(&cpu_buffer->reader_lock, flags);
> +
> + /* Free old sub buffers */
> + list_for_each_entry_safe(bpage, tmp, &old_pages, list) {
> + list_del_init(&bpage->list);
> + free_buffer_page(bpage);
> + }
> + free_pages((unsigned long)old_free_data_page, old_order);
> +
> rb_check_pages(cpu_buffer);
> }
>
prev parent reply other threads:[~2024-10-11 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 23:58 Steven Rostedt
2024-10-11 8:05 ` Petr Pavlu
2024-10-11 14:01 ` Steven Rostedt
2024-10-11 14:48 ` Steven Rostedt
2024-10-11 15:20 ` Petr Pavlu
2024-10-11 16:44 ` Steven Rostedt
2024-10-11 16:53 ` 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=20241011125346.5edffba6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=petr.pavlu@suse.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®