Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination

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

 



On Fri, 2020-01-17 at 12:49 +0000, David Howells wrote:
> It may be worth a discussion of whether linkat() could be given a
> flag to
> allow the destination to be replaced or if a new syscall should be
> made for
> this - or whether it should be disallowed entirely.
> 
> A set of patches has been posted by Omar Sandoval that makes this
> possible:
> 
>     
> https://lore.kernel.org/linux-fsdevel/cover.1524549513.git.osandov@xxxxxx/
> 
> though it only includes filesystem support for btrfs.
> 
> This could be useful for cachefiles:
> 
> 	
> https://lore.kernel.org/linux-fsdevel/3326.1579019665@xxxxxxxxxxxxxxxxxxxxxx/
> 
> and overlayfs.
> 

That seems to me like a "just go ahead and do it if you can justify it"
kind of thing. It has plenty of precedent, and fits easily into the
existing syscall, so why do we need a face-to-face discussion?

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@xxxxxxxxxxxxxxx






[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