diff options
| author | Jeff Layton <jlayton@redhat.com> | 2016-10-26 14:26:40 +0300 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2016-11-01 22:47:43 +0300 |
| commit | 8f97514b423a0983e4c600099882a9c6613142d2 (patch) | |
| tree | b16f551114bf911b4b5bd914ceedb94434226279 /fs/nfsd/nfs4layouts.c | |
| parent | f46c445b79906a9da55c13e0a6f6b6a006b892fe (diff) | |
| download | linux-8f97514b423a0983e4c600099882a9c6613142d2.tar.xz | |
nfsd: more robust allocation failure handling in nfsd_reply_cache_init
Currently, we try to allocate the cache as a single, large chunk, which
can fail if no big chunks of memory are available. We _do_ try to size
it according to the amount of memory in the box, but if the server is
started well after boot time, then the allocation can fail due to memory
fragmentation.
Fall back to doing a vzalloc if the kcalloc fails, and switch the
shutdown code to do a kvfree to handle freeing correctly.
Reported-by: Olaf Hering <olaf@aepfle.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd/nfs4layouts.c')
0 files changed, 0 insertions, 0 deletions