diff options
| author | Christoph Hellwig <[email protected]> | 2022-11-01 16:00:37 +0100 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2022-11-02 08:32:31 -0600 |
| commit | 71b26083d59cd4ab22489829ffe7d4ead93f5546 (patch) | |
| tree | 6052a741a07c4b624c705bb364e5c9fa62fccecf /tools/perf/scripts/python/bin/flamegraph-record | |
| parent | aa625117d6f67e33fab280358855fdd332bb20ab (diff) | |
block: set the disk capacity to 0 in blk_mark_disk_dead
nvme and xen-blkfront are already doing this to stop buffered writes from
creating dirty pages that can't be written out later. Move it to the
common code.
This also removes the comment about the ordering from nvme, as bd_mutex
not only is gone entirely, but also hasn't been used for locking updates
to the disk size long before that, and thus the ordering requirement
documented there doesn't apply any more.
Signed-off-by: Christoph Hellwig <[email protected]>
Reviewed-by: Keith Busch <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Reviewed-by: Ming Lei <[email protected]>
Reviewed-by: Chao Leng <[email protected]>
Reviewed-by: Chaitanya Kulkarni <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/flamegraph-record')
0 files changed, 0 insertions, 0 deletions