On Wed, Jul 24, 2019 at 09:53:33AM -0400, Jeff Mahoney wrote: > On 5/17/19 9:12 AM, David Sterba wrote: > > On Wed, May 15, 2019 at 03:45:13PM +0100, Filipe Manana wrote: > >>>>> And running delayed refs can dirty more block groups as well. > >>>>> At this point shouldn't we loop running delayed refs until no more > >>>>> dirty block groups exist? Just like in the kernel. > >>>> > >>>> Right. This is another argument for code sharing between the kernel and > >>>> userspace. > >>> > >>> Sharing code in this function would be really hard, I've implemented the > >>> loop in commit in progs. > >> > >> Shouldn't the new patch version be sent to the list for review? > >> It doesn't seem to be a trivial change on first through. > > > > Ok, I've removed the patches from devel and will send them once the > > release is done. > > > > Hi Dave - > > Did this ever get revisited?
No, but Qu sent the fix, that's now in devel.
