diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2023-05-18 20:45:50 +0300 |
|---|---|---|
| committer | Chuck Lever <chuck.lever@oracle.com> | 2023-06-11 23:37:45 +0300 |
| commit | ed4a567a179ec15c15f78fa60ca6de9cc4f34897 (patch) | |
| tree | 02b219b7a15e64bfdcb3c40c9e74f46f7bcf4fa8 /fs/nfsd/nfs3proc.c | |
| parent | ba21e20b309564c64761f4953db4456ec8c4e49c (diff) | |
| download | linux-ed4a567a179ec15c15f78fa60ca6de9cc4f34897.tar.xz | |
NFSD: Update rq_next_page between COMPOUND operations
A GETATTR with a large result can advance xdr->page_ptr without
updating rq_next_page. If a splice READ follows that GETATTR in the
COMPOUND, nfsd_splice_actor can start splicing at the wrong page.
I've also seen READLINK and READDIR leave rq_next_page in an
unmodified state.
There are potentially a myriad of combinations like this, so play it
safe: move the rq_next_page update to nfsd4_encode_operation.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'fs/nfsd/nfs3proc.c')
0 files changed, 0 insertions, 0 deletions