Re: [WTF] ... is going on with current->fs->{root,mnt} accesses in pohmelfs

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

 



On Wed, Feb 10, 2010 at 11:59:39AM +0000, Al Viro (viro@xxxxxxxxxxxxxxxxxx) wrote:
> > Let me guess... Mmmm, it was in the yesterday newspaper, I remember.
> > Maybe when we chroot somewhere. I meant not mounted fs root, but
> > thread's root.
> 
> Why would a filesystem give a damn about the chroot of syscall originator
> in the first place?

That's the point - it is not needed.

> > > Why not use the dentries you've been given by VFS?
> > 
> > At writeback we do not have parents, so must find a path somehow.
> 
> Most of the places do have those just fine and unlike the writeback,
> rename et.al. really care which pathname is being dealt with...

POHMELFS uses writeback cache also for metadata, so effectively most of
such operations are also postponed. Later I turned that off though.

> BTW, what prevents writeback vs. rename races?

There are proper locks for such operations.

-- 
	Evgeniy Polyakov
--
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