diff options
| author | NeilBrown <neil@brown.name> | 2026-07-17 19:28:03 +1000 |
|---|---|---|
| committer | Chuck Lever <cel@kernel.org> | 2026-08-26 16:40:38 -0400 |
| commit | 0165a5807b5e65b71f5d3377f6d7cf65d455a778 (patch) | |
| tree | 935e507d74761fec12793eb68b0a3c065a4f639a /scripts/Makefile.thinlto | |
| parent | 13bcdb085c17229f429169ee675afceb04034455 (diff) | |
| download | linux-next-0165a5807b5e65b71f5d3377f6d7cf65d455a778.tar.gz linux-next-0165a5807b5e65b71f5d3377f6d7cf65d455a778.zip | |
nfsd: reduce want-write range in nfsd4_create_file()
nfsd4_create_file() needs write access to the mount for two purposes:
1/ to create/open the file.
2/ to set attributes on the newly created (or pre-existing) file.
Currently this is all handled by holding the write access across the
open and the setattr. A subsequent patch will necessarily change how
write access is gained for the open. So we reduce the range for the
first want_write, and add another one to cover setattr. If we failed to
get write access, it is only fatal if there were attrs to set.
We call nfsd_create_setattr() if at all possible, even when no attrs, as
it also calls commit_metadata and we need to be certain that the file
creation has been synced. If the mount became read-only since the
creation happened, we can safely assume that the sync happened as part
of that.
Signed-off-by: NeilBrown <neil@brown.name>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Link: https://patch.msgid.link/20260717093001.1972119-16-neilb@ownmail.net
Signed-off-by: Chuck Lever <cel@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
