diff options
| author |   Nathaniel Clark <nathaniel.l.clark@intel.com> | 2017-07-26 11:22:23 -0400 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-07-30 08:08:31 -0700 |
| commit | 476f575cf0706fe94a6b4709b01a6def1169df02 (patch) | |
| tree | 10389d79dafae36c58344f926f202e98751a39e6 /tools/perf/scripts/python/stackcollapse.py | |
| parent | staging: lustre: lmv: assume a real connection in lmv_connect() (diff) | |
| download | wireguard-linux-476f575cf0706fe94a6b4709b01a6def1169df02.tar.xz wireguard-linux-476f575cf0706fe94a6b4709b01a6def1169df02.zip | |
staging: lustre: lov: Ensure correct operation for large object sizes
If a backing filesystem (ZFS) returns that it supports very large
(LLONG_MAX) object sizes, that should be correctly supported. This
fixes the check for unitialized stripe_maxbytes in
lsm_unpackmd_common(), so that ZFS can return LLONG_MAX and it will be
okay. This issue is excersized by writing to or past the 2TB boundry
of a singly stripped file.
Signed-off-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7890
Reviewed-on: http://review.whamcloud.com/19066
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Jinshan Xiong <jinshan.xiong@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: James Simmons <jsimmons@infradead.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions