diff options
| author | Neil Brown <neilb@suse.com> | 2016-12-22 20:38:06 +0300 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2017-01-31 20:31:53 +0300 |
| commit | 2b477c00f3bd87c3286f5940cb4174d8b01ee0d5 (patch) | |
| tree | c6de85ae00a8251c4e7d5093a2881de61b487003 /mm/kmemleak-test.c | |
| parent | 034dd34ff4916ec1f8f74e39ca3efb04eab2f791 (diff) | |
| download | linux-2b477c00f3bd87c3286f5940cb4174d8b01ee0d5.tar.xz | |
svcrpc: free contexts immediately on PROC_DESTROY
We currently handle a client PROC_DESTROY request by turning it
CACHE_NEGATIVE, setting the expired time to now, and then waiting for
cache_clean to clean it up later. Since we forgot to set the cache's
nextcheck value, that could take up to 30 minutes. Also, though there's
probably no real bug in this case, setting CACHE_NEGATIVE directly like
this probably isn't a great idea in general.
So let's just remove the entry from the cache directly, and move this
bit of cache manipulation to a helper function.
Signed-off-by: Neil Brown <neilb@suse.com>
Reported-by: Andy Adamson <andros@netapp.com>
Signed-off-by: Andy Adamson <andros@netapp.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'mm/kmemleak-test.c')
0 files changed, 0 insertions, 0 deletions