Re: [LTP] 56cbb429d9: ltp.fs_fill.fail

On Thu, Jul 25, 2019 at 07:04:28PM +0100, Al Viro wrote: > On Thu, Jul 25, 2019 at 09:32:13AM -0700, Linus Torvalds wrote: > > On Thu, Jul 25, 2019 at 6:26 AM Cyril Hrubis wrote: > > > > > > This looks like mkfs.vfat got EBUSY after the loop device was > > > succesfully umounted. > > > > Hmm.

Re: [LTP] 56cbb429d9: ltp.fs_fill.fail

On Thu, Jul 25, 2019 at 09:32:13AM -0700, Linus Torvalds wrote: > On Thu, Jul 25, 2019 at 6:26 AM Cyril Hrubis wrote: > > > > This looks like mkfs.vfat got EBUSY after the loop device was > > succesfully umounted. > > Hmm. Smells like the RCU-delaying got triggered again. > > We have that

Re: [LTP] 56cbb429d9: ltp.fs_fill.fail

On Thu, Jul 25, 2019 at 6:26 AM Cyril Hrubis wrote: > > This looks like mkfs.vfat got EBUSY after the loop device was > succesfully umounted. Hmm. Smells like the RCU-delaying got triggered again. We have that "synchronize_rcu_expedited()" in namespace_unlock(), which is so that everything

Re: [LTP] 56cbb429d9: ltp.fs_fill.fail

Hi! > tst_test.c:1161: INFO: Testing on vfat > tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts='' > mkfs.vfat: unable to open /dev/loop0: Device or resource busy > tst_mkfs.c:101: BROK: mkfs.vfat:1: tst_test.c failed with 741 This looks like mkfs.vfat got EBUSY after the