Re: writeback hang in current mainline

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 26 2010, Christoph Hellwig wrote:
> On Wed, May 26, 2010 at 07:18:15PM +0200, Jens Axboe wrote:
> > OK. From your previous mail:
> > 
> >         For now I would recommend to revert
> >         21c12849fef73efc9a898b6702fe421fd774f515 and
> >         29c795f02e68ecd7bb1374844d3e55e882ac158f,
> >         which makes xfstests run fine for me.
> > 
> > Just to ensure we are on the same page, what commits are these? They are
> > not valid shas in Linus' tree. Did you mean
> 
> Sorry, those were my local revert commits.
> 
> > 
> >         e913fc825dc685a444cb4c1d0f9d32f372f59861
> >         7c8a3554c683f512dbcee26faedb42e4c05f12fa
> 
> Exactly!

Makes sense then. So the change from those commits (with the fixes from
today) ensures that we properly do WB_SYNC_NONE writeback when
sb->s_umount is held instead of just skipping those inodes. The question
is, is that exposing some other bug or is the code still buggy...

You said that you could not get a backtrace when the test hung, were you
able to get anything out of it?

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux