Re: [PATCH] ring-buffer: serialize read-page order with subbuffer resize
Yousef Alhouseen <[email protected]>
| Newsgroups | org.kernel.vger.linux-trace-kernel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAMuQ4bWw1mmwK+aJN3024s+rGWCx-WfxvmpqkR3c_u8JND7fKA@mail.gmail.com> |
Not yet. The mutex-based draft isn't suitable; I still need to implement and test the resize-in-progress flag design you requested. I'll send v2 only after that is done. Thanks, Yousef On Tue, 7 Jul 2026 10:36:19 -0400, Steven Rostedt <[email protected]> wrote: > On Tue, 30 Jun 2026 14:16:48 -0700 > Yousef Alhouseen <[email protected]> wrote: > > > Agreed. I’ll add an explicit resize-in-progress flag, set it around > > the order transition, and make the external read-page > > allocation/free/read paths reject work while it is set. I’ll check the > > flag under the locks that serialize each path so it cannot race the > > transition, then compile and test the resulting v2. > > Did you ever get around to sending a v2? > > -- Steve