diff options
| author | NeilBrown <neil@brown.name> | 2026-07-17 19:27:58 +1000 |
|---|---|---|
| committer | Chuck Lever <cel@kernel.org> | 2026-08-26 16:40:27 -0400 |
| commit | 4d6f937163b88d4ff78c72bfcaa35b084909b109 (patch) | |
| tree | b5ea4e76569055c45a3037211d615e21b7ef2c2e /scripts/Makefile.thinlto | |
| parent | 3c34beb9b5eb490a4b433ba2db0693afcbcb5d90 (diff) | |
| download | linux-next-4d6f937163b88d4ff78c72bfcaa35b084909b109.tar.gz linux-next-4d6f937163b88d4ff78c72bfcaa35b084909b109.zip | |
nfsd: fh_want_write) failure need not be immediately fatal for nfsd4_create_file()
If nfsd4_create_file() is asked to create a file, then failure to get
write access to the mount need not be fatal if the file already exists.
So we can delay handling the error until it is known if creation was
needed, just like with the error from testing for write permission in
parent.
This is similar to want_write error handling in lookup_open() in
fs/namei.c.
Note that getting mnt write access to support O_RDWR is handled
separately in do_dentry_open(), and op_truncate is handled in
do_open_permission(), so nfsd doesn't need to be concerned
with these. It only needs to be concerned with creation, and setattr.
Signed-off-by: NeilBrown <neil@brown.name>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Link: https://patch.msgid.link/20260717093001.1972119-11-neilb@ownmail.net
Signed-off-by: Chuck Lever <cel@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
