Re: Locking between writeback and truncate paths?

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

 



On Sun, Apr 25, 2010 at 08:32:40PM -0400, Theodore Ts'o wrote:
> Any thoughts or suggestions would be greatly appreciated.  I've looked
> at the xfs and btrfs code for some ideas, but dealing with current
> writeback and truncate is nasty, especially if there's a subsequent
> delalloc write happening in parallel with the writeback and immediately
> after the truncate.  After studying the code quite extensively over the
> weekend, I'm still not entirely sure that XFS and btrfs gets this case
> right (I know ext4 currently doesn't).  Of course, it's not clear
> whether users will trip against this in practice, but it's nevertheless
> still a botch, and I'm wondering if it's simpler to avoid the concurrent
> vmtruncate/writeback case entirely.

What case are you concerned that is XFS not getting right?

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx
--
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