diff options
| author | Bobi Jam <bobijam.xu@intel.com> | 2016-12-03 03:53:24 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-12-06 12:56:29 +0300 |
| commit | 9fd14479a6d8dc22bb3802686a8a44cde1d4aae9 (patch) | |
| tree | 2c71421153aa4209aa5dc6a7c3a2b575569c1070 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | db2472b0b64cc8531a0e0f0148645f9841bd1f27 (diff) | |
| download | linux-9fd14479a6d8dc22bb3802686a8a44cde1d4aae9.tar.xz | |
staging: lustre: clio: remove mtime check in vvp_io_fault_start()
In fault IO initialization, inode's mtime is saved, and after
getting locks, when the IO is about to start, vvp_io_fault_start()
checks the mtime's intactness.
It's a false alarm, since the timestamp from MDS could be stale,
we maintain mtime mainly on OST objects, and if the check in
vvp_io_fault_start() happens before mtime on OST objects are merged,
it will get wrong timestamp from the inode, even the timestamp it
fetched in vvp_io_fault_init() could be wrong in the first place.
This patch remove the mtime check in vvp_io_fault_start().
Signed-off-by: Bobi Jam <bobijam.xu@intel.com>
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7198
Reviewed-on: http://review.whamcloud.com/19162
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Jinshan Xiong <jinshan.xiong@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/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions