On Tue, 26 May 2026 13:42:31 -0400 Steven Rostedt <[email protected]> wrote:
> On Tue, 26 May 2026 14:17:46 +0900 > Masami Hiramatsu (Google) <[email protected]> wrote: > > > On Fri, 22 May 2026 13:08:57 -0400 > > Steven Rostedt <[email protected]> wrote: > > > > > This is to make the persistent ring buffer more robust when sub-buffers > > > are detected to be corrupted. Instead of invalidating the entire buffer, > > > just invalidate the individual sub-buffers. > > > > > > I started with Masami's patches and modified some from Sashiko reviews. > > > I added a few patches to display the dropped events when the persistent > > > ring buffers validation checks found sub-buffers were dropped due to being > > > corrupted data. > > > > It seems that Sashiko still marks it "Incompleted". > > Maybe we need base-commit: tag in this cover mail? > > I also guess that this series does not use "In-Reply-To:" but > > only uses "References:" tag in the mail header. I guess > > Sashiko's mail header parser missed it. > > But this applies to mainline. I'm not sure why it's having problems. Yeah, I confirmed this series can be applied to linus mainline tree. I meant that the Sashiko's email header parser may failed to parse the thread correctly. - The patches in this series are listed separately. https://sashiko.dev/#/?list=org.kernel.vger.linux-trace-kernel - The cover mail also listed and the page has "Thread" list but it only has replies to the cover mail. No other patches. https://sashiko.dev/#/patchset/20260522170857.263969486%40kernel.org - v18 seems correctly parsed, which has "In-Reply-To:" tag in the mail header. https://sashiko.dev/#/patchset/177701351903.2223789.17087009302463188638.stgit%40mhiramat.tok.corp.google.com So I guess Sashiko's email header parser does not correctly handle the "References:" tag for recognizing thread. Thank you, > > -- Steve -- Masami Hiramatsu (Google) <[email protected]>
