Re: [PATCH v12 0/4] ring-buffer: Making persistent ring buffers robust

From
Masami Hiramatsu (Google) <mhiramat@kernel.org>
Date
2026-03-25 00:13:07
Also in
lkml
Reply to
Masami Hiramatsu (Google), 2026-03-24
On Wed, 25 Mar 2026 08:56:44 +0900
Masami Hiramatsu (Google) [off-list ref] wrote:
On Tue, 24 Mar 2026 17:25:57 -0400
Steven Rostedt [off-list ref] wrote:
quoted
On Tue, 24 Mar 2026 09:00:03 +0900
"Masami Hiramatsu (Google)" [off-list ref] wrote:
quoted
Hi,

Here is the 12th version of improvement patches for making persistent
ring buffers robust to failures.
The previous version is here:

https://lore.kernel.org/all/177391152793.193994.8986943289250629418.stgit@mhiramat.tok.corp.google.com/ (local)


In this version, I rebased it on tracing/fixes branch (thus
the first fix patch has been removed) and fixed
a build error which came from a copy-paste mistake.
Hi Masami,

Can you rebase this on the ring-buffer/for-next branch?

It has the remote updates for pkvm tracing, and there's some conflicts.
That branch is also used by the ARM tree so it can't be rebased.
OK, let me rebase the series on it.
I found the branch does not have a fix [1] and it makes a conflict with
[2/4]. Can you update it to merge the trace/fixes branch?

[1] f35dbac69421 ("ring-buffer: Fix to update per-subbuf entries of persistent ring buffer")

I can send a series on ring-buffer/for-next but I think it may
cause the same conflict on git-pull later.

Thanks,
Thanks!
quoted
Thanks,

-- Steve

-- 
Masami Hiramatsu (Google) [off-list ref]

-- 
Masami Hiramatsu (Google) [off-list ref]
Thread (10 messages) 10 messages, 2 authors, last reply 2026-03-25
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help