nfsd4: decoding errors can still be cached and require space

Browse source

Currently a non-idempotent op reply may be cached if it fails in the
proc code but not if it fails at xdr decoding.  I doubt there are any
xdr-decoding-time errors that would make this a problem in practice, so
this probably isn't a serious bug.

The space estimates should also take into account space required for
encoding of error returns.  Again, not a practical problem, though it
would become one after future patches which will tighten the space
estimates.

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

...

This commit is contained in:

J. Bruce Fields 2014-05-19 12:27:11 -04:00

parent f34e432b67

commit e372ba60de

2 changed files with 7 additions and 5 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

2

fs/nfsd/nfs4proc.c

View file

10

fs/nfsd/nfs4xdr.c

View file