On Thu, Mar 08, 2018 at 10:01:42PM +0000, Trond Myklebust wrote: > On Thu, 2018-03-08 at 16:39 -0500, bfields@xxxxxxxxxxxx wrote: > > On Thu, Mar 08, 2018 at 08:09:01AM -0500, Scott Mayhew wrote: > > > Yes, this works. I ran it through a dozen fio runs on v4.1 and > > > 1000 runs > > > of generic/247 on v3/v4.0/v4.1/v4.2 and didn't see any EBUSY > > > errors. > > > Also ran the xfstests "quick" group (~80-90 tests) plus generic/074 > > > on > > > v3/v4.0/v4.1/v4.2. Finally, I double checked the panic on umount > > > issue > > > that dc4fd9ab01ab3 fixed and that still works too. > > > > Works for me too. > > > > (Yeah, I see there's a new patch. Testing queued up but not run > > yet...). > > Sorry for pulling the "new patch switch" on you both, but I figured it > would be better to re-examine where the requirement for the dirty flag > is coming from, and to ensure that we meet that requirement once and > for all. No problem. My tests are passing on the new patch as well. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
