block/loop: handle discard/zeroout error
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | block/loop: don't hijack error numberdrivers/ | +2 | 0 replies | |
| 2/3 | block/loop: use FALLOC_FL_ZERO_RANGE for REQ_OP_WRITE_ZEROESdrivers/ | +3 | 0 replies | |
| 3/3 | block/loop: suppress discard IO error messagedrivers/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3]block/loop: handle discard/zeroout error
Fix some problems when setting up loop device with a block device as back file and create/mount ext4 in the loop device.
BTW: blkdev_issue_zeroout retries if we immediately find the device doesn't support zeroout, but it doesn't retry if submit_bio_wait returns -EOPNOTSUPP. Is this correct behavior?
Thanks,
Shaohua
Shaohua Li (3):
block/loop: don't hijack error number
block/loop: use FALLOC_FL_ZERO_RANGE for REQ_OP_WRITE_ZEROES block/loop: suppress discard IO error message
drivers/block/loop.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
Signature · 1 line
2.9.5