diff options
| author |   Chuck Lever <chuck.lever@oracle.com> | 2025-06-10 12:05:09 -0400 |
|---|---|---|
| committer | Chuck Lever <chuck.lever@oracle.com> | 2025-07-14 12:46:41 -0400 |
| commit | 48aab1606fa80027143a445224f552b4eeea845b (patch) | |
| tree | 30c43cf5579297856ccfb658b7f4c29fa18b6f45 /tools/perf/scripts/python | |
| parent | NFSD: Make nfsd_genl_rqstp::rq_ops array best-effort (diff) | |
| download | wireguard-linux-48aab1606fa80027143a445224f552b4eeea845b.tar.xz wireguard-linux-48aab1606fa80027143a445224f552b4eeea845b.zip | |
NFSD: Remove the cap on number of operations per NFSv4 COMPOUND
This limit has always been a sanity check; in nearly all cases a
large COMPOUND is a sign of a malfunctioning client. The only real
limit on COMPOUND size and complexity is the size of NFSD's send
and receive buffers.
However, there are a few cases where a large COMPOUND is sane. For
example, when a client implementation wants to walk down a long file
pathname in a single round trip.
A small risk is that now a client can construct a COMPOUND request
that can keep a single nfsd thread busy for quite some time.
Suggested-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions