| commit | c966c0b8414ef0a041b1a8d5261c9eccd4d39d99 | |
| author | Mark Vitale <mvitale@sinenomine.net> | |
| Tue, 12 Jan 2016 22:50:36 +0000 (12 17:50 -0500) | ||
| committer | Benjamin Kaduk <kaduk@mit.edu> | |
| Sun, 11 Dec 2016 21:53:33 +0000 (11 16:53 -0500) | ||
| tree | 160c851d3b7bce580f4f11698d6dba7fa91475d4 | treesnapshot (tar.gz zip) |
| parent | 7442752ba6ad618bcdf2185f699d90c56838e89e | commitdiff |
afs: fs getcacheparms miscounts zero-length dcaches
When fs getcacheparms is issued with the -excessive option, it
tabulates all in-memory dcaches ("DCentries") by size.
dcaches with validPos == 0 were being tabulated in the 4k-16k bucket.
Fix the first comparison in the 'sieve' so these dcaches will be counted
in the correct 0-4k bucket instead.
Introduced by commit 176c2fddb95ced6c13e04e7492fc09b5551f273c
Change-Id: I60acb0f115dad9f7951f0b17e5b3e37dc94321b9
Reviewed-on: https://gerrit.openafs.org/12346
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
When fs getcacheparms is issued with the -excessive option, it
tabulates all in-memory dcaches ("DCentries") by size.
dcaches with validPos == 0 were being tabulated in the 4k-16k bucket.
Fix the first comparison in the 'sieve' so these dcaches will be counted
in the correct 0-4k bucket instead.
Introduced by commit 176c2fddb95ced6c13e04e7492fc09b5551f273c
Change-Id: I60acb0f115dad9f7951f0b17e5b3e37dc94321b9
Reviewed-on: https://gerrit.openafs.org/12346
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
| src/afs/afs_pioctl.c | diffblobblamehistory |