Re: [PATCH v2 0/4] VFS: prepare for changes to directory locking
Christian Brauner <[email protected]>
| Newsgroups | org.kernel.vger.linux-fsdevel |
|---|---|
| Message-ID | <20260813-bronzen-fernhalten-perfide-99cf86e3a487@brauner> |
On 2026-08-11 20:29 +1000, NeilBrown wrote: > On Tue, 11 Aug 2026, Christian Brauner wrote: > > On Wed, Aug 05, 2026 at 01:11:55PM +1000, NeilBrown wrote: > > > On Thu, 23 Jul 2026, NeilBrown wrote: > > > > Thanks a lot to Christian for the review. I have address all this > > > > issues found. > > > > > > Hi, > > > has anyone had a chance to review? Is there any change this could land > > > in the next -rc1 ?? > > > > I haven't gotten around to it and we're kinda cutting it very close. > > I have reviewed prior versions so I'm not unfamiliar with it. If there > > are no real costs to pushing it to next cycle I'd prefer that. > > > > I would be disappointed to lose another cycle.... > These were, I thought, ready to go in the previous cycle but they got > little or no review and Al only took one patch (the d_alloc_parallel > wait-queue change) for reasons that were not made clear. Yes, I hinted at that in one of my earlier replies that there were some api quibbles some cycles ago on whether this direction was right or not. > I had hoped these few could land this time round so that I could post > patches to maintainers of various filesystems to start using the new > APIs. > > If you would be happy to take those follow-on patches to various > filesystems together with these preparatory patches in the next cycle, > then I should still be able to get everything ready for the next step > without losing a cycle. Would that be OK? Yes, that would be acceptable.