nfsd4: don't try to encode conflicting owner if low on space

Browse source

I ran into this corner case in testing: in theory clients can provide
state owners up to 1024 bytes long.  In the sessions case there might be
a risk of this pushing us over the DRC slot size.

The conflicting owner isn't really that important, so let's humor a
client that provides a small maxresponsize_cached by allowing ourselves
to return without the conflicting owner instead of outright failing the
operation.

Signed-off-by: J. Bruce Fields <bfields@redhat.com>

...

This commit is contained in:

J. Bruce Fields 2014-03-10 12:19:10 -04:00

parent f5236013a2

commit 8c7424cff6

2 changed files with 15 additions and 4 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

fs/nfsd/nfs4proc.c

View file

16

fs/nfsd/nfs4xdr.c

View file