Chuck Lever ed4a567a17 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>
2023-06-11 16:37:45 -04:00
..
2023-03-10 09:38:47 -05:00
2021-10-02 15:51:10 -04:00
2023-02-20 11:10:38 -08:00
2023-02-22 14:21:40 -08:00
2023-02-22 14:21:40 -08:00
2023-02-22 14:21:40 -08:00
2022-10-20 10:13:27 +02:00
2023-02-22 14:21:40 -08:00
2023-06-05 09:01:43 -04:00
2023-02-20 11:53:11 -08:00
2023-02-22 14:21:40 -08:00
2021-12-13 13:42:51 -05:00
2023-06-05 09:01:43 -04:00
2023-06-05 09:01:41 -04:00
2023-02-20 09:20:21 -05:00