diff options
| author | Chuck Lever <cel@kernel.org> | 2026-07-23 14:20:43 -0400 |
|---|---|---|
| committer | Chuck Lever <cel@kernel.org> | 2026-08-26 16:41:18 -0400 |
| commit | 9ff1cfefd29132d349695ccd7f002d9c59a0849a (patch) | |
| tree | 81e5f2169d16cf747c8cde9c77dc962ae4b5ae00 /scripts/objdiff | |
| parent | cddeaf87ef931685fde88dac09adf543d4a36233 (diff) | |
| download | linux-next-9ff1cfefd29132d349695ccd7f002d9c59a0849a.tar.gz linux-next-9ff1cfefd29132d349695ccd7f002d9c59a0849a.zip | |
NFSD: Replace nfsd_write()'s "stable" argument with "iocb_flags"
The current nfsd_write() API is not NFS version-agnostic, as it
relies on callers to pass an NFSv3 stable_how value to determine
the persistence of the requested WRITE. NFSv2 does not use a
stable-how value on the wire, and NFSv4 has its own stable_how4
(though stable_how and stable_how4 happen to share the same
numeric values).
To remove the dependence on NFSv3-specific XDR values from NFSD's
generic VFS APIs, replace nfsd_write()'s stable argument with an
argument that passes a set of IOCB flags instead of an XDR-defined
value.
The NFSv4 WRITE and COPY paths had been borrowing the NFSv3
stable_how constants for their own on-the-wire stable values,
relying on the numeric coincidence noted above. Convert those
sites to the stable_how4 enumerators so the v4 code expresses
its own protocol's values directly, with no change in behavior.
While here, bound-check the decoded NFSv3 WRITE stable value, as
the NFSv4 WRITE decoder already does, and make the nfsd3_writeargs
stable field unsigned to suit.
The larger benefit is one less NFSv4 dependency on nfs3.h.
Link: https://patch.msgid.link/20260723182043.990391-3-cel@kernel.org
Signed-off-by: Chuck Lever <cel@kernel.org>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions
