[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231129-birnen-erwandern-92bfa945d3e0@brauner>
Date: Wed, 29 Nov 2023 11:21:10 +0100
From: Christian Brauner <brauner@...nel.org>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: linux-fsdevel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>, tytso@....edu,
linux-f2fs-devel@...ts.sourceforge.net, ebiggers@...nel.org,
jaegeuk@...nel.org, linux-ext4@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Miklos Szeredi <miklos@...redi.hu>,
Gabriel Krisman Bertazi <gabriel@...sman.be>
Subject: Re: fun with d_invalidate() vs. d_splice_alias() was Re: [f2fs-dev]
[PATCH v6 0/9] Support negative dentries on case-insensitive ext4 and f2fs
> 2) lookup fails. It's already possible; e.g. if server has
I think that's the sanest option. The other options seem even less
intuitive.
> not fatal. The trouble is, that won't be a transient failure -
> not until somebody tries to look the old location up.
Eh, nfs semantics are quite special anyway already. I'd rather have that
in lookup than more magic involving moving mounts around or having them
disappear (Yes, we have the detach semantics on removal but that's
different.).
Powered by blists - more mailing lists