mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Pavlu <petr.pavlu@suse.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Petr Pavlu <petr.pavlu@suse.com>
Subject: [PATCH 0/2] ring-buffer: Fix a race between readers and resize checks
Date: Fri, 17 May 2024 15:40:06 +0200	[thread overview]
Message-ID: <20240517134008.24529-1-petr.pavlu@suse.com> (raw)

Fix a race between a reader swapping a new reader page into the
ring-buffer from rb_get_reader_page() and the rb_check_pages() check
invoked at the end of the resize operation in ring_buffer_resize().

Note that a similar problem with rb_check_pages() being executed with
concurrent readers looks to exist for ring_buffer_subbuf_order_set()
too. I plan to tackle it in a separate series.

Petr Pavlu (2):
  ring-buffer: Correct stale comments related to non-consuming readers
  ring-buffer: Fix a race between readers and resize checks

 kernel/trace/ring_buffer.c | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)


base-commit: ea5f6ad9ad9645733b72ab53a98e719b460d36a6
-- 
2.35.3


             reply	other threads:[~2024-05-17 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 13:40 Petr Pavlu [this message]
2024-05-17 13:40 ` [PATCH 1/2] ring-buffer: Correct stale comments related to non-consuming readers Petr Pavlu
2024-05-17 13:40 ` [PATCH 2/2] ring-buffer: Fix a race between readers and resize checks Petr Pavlu
2024-05-20 13:50   ` Steven Rostedt
2024-05-27  9:36     ` Petr Pavlu
2024-05-27 23:43       ` Steven Rostedt
2024-06-07  8:29         ` Petr Pavlu
2024-06-10 15:56           ` Steven Rostedt

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=20240517134008.24529-1-petr.pavlu@suse.com \
    --to=petr.pavlu@suse.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 \
    /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®