diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2023-05-18 13:46:03 -0400 |
---|---|---|
committer | Chuck Lever <chuck.lever@oracle.com> | 2023-06-11 16:37:46 -0400 |
commit | 703d7521555504b3a316b105b4806d641b7ebc76 (patch) | |
tree | 215d066add0d132fcfdbab631769ed4e617e5ad6 /arch/nios2/kernel | |
parent | 507df40ebf31655203dd05e6e31db5849a83347a (diff) | |
download | linux-703d7521555504b3a316b105b4806d641b7ebc76.tar.gz linux-703d7521555504b3a316b105b4806d641b7ebc76.tar.bz2 linux-703d7521555504b3a316b105b4806d641b7ebc76.zip |
NFSD: Hoist rq_vec preparation into nfsd_read() [step two]
Now that the preparation of an rq_vec has been removed from the
generic read path, nfsd_splice_read() no longer needs to reset
rq_next_page.
nfsd4_encode_read() calls nfsd_splice_read() directly. As far as I
can ascertain, resetting rq_next_page for NFSv4 splice reads is
unnecessary because rq_next_page is already set correctly.
Moreover, resetting it might even be incorrect if previous
operations in the COMPOUND have already consumed at least a page of
the send buffer. I would expect that the result would be encoding
the READ payload over previously-encoded results.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'arch/nios2/kernel')
0 files changed, 0 insertions, 0 deletions