diff options
| author | Christoph Hellwig <[email protected]> | 2018-07-11 22:25:58 -0700 |
|---|---|---|
| committer | Darrick J. Wong <[email protected]> | 2018-07-11 22:25:58 -0700 |
| commit | c57371a16d074bb4eafe6b73f29360085ecb2064 (patch) | |
| tree | 124ef8875e28579134477ffcc51409e0586cc2f5 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 91cdfd1761659f338e673aca72af3d0d50b88847 (diff) | |
xfs: don't clear imap_valid for a non-uptodate buffers
Finding a buffer that isn't uptodate doesn't invalidate the mapping for
any given block. The last_sector check will already take care of starting
another ioend as soon as we find any non-update buffer, and if the current
mapping doesn't include the next uptodate buffer the xfs_imap_valid check
will take care of it.
Signed-off-by: Christoph Hellwig <[email protected]>
Reviewed-by: Brian Foster <[email protected]>
Reviewed-by: Darrick J. Wong <[email protected]>
Signed-off-by: Darrick J. Wong <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions