Skip to content

block: fix I/O errors in BLKRRPART

Minwoo Im linux-block linux-fsdevel linux-nvme 5 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v6 Latest1 patch 0 repliesNew
  2. v51 patch 0 repliesSuperseded
  3. v41 patch 1 replySuperseded
Earlier versions · 2
VersionPostedPatchesRepliesStatus
v3 RFC1 patch5 repliesSuperseded
v2 RFC1 patch3 repliesSuperseded

Changes in v6 from the cover letter

- Rebased on for-next

Patches in v6 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/1block: reject I/O for same fd if block size changedblock/blk-settings.c block/partitions/core.c fs/block_dev.c +1 more+24 -00 replies

Reviews trailers per patch

The patch has a Reviewed-by or Acked-by.

PatchChristoph Hellwig
1/1R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v6 thread

Cover letter [PATCH V6 0/1] block: fix I/O errors in BLKRRPART

Hello,

(This series is just RESEND with rebasing it on for-next)

This patch fixes I/O errors during BLKRRPART ioctl() behavior right
after format operation that changed logical block size of the block device with a same file descriptor opened.

Testcase:

The following testcase is a case of NVMe namespace with the following
conditions:

- Current LBA format is lbaf=0 (512 bytes logical block size)
- LBA Format(lbaf=1) has 4096 bytes logical block size

  # Format block device logical block size 512B to 4096B                                                                                                                                                                                                                                                                                                                                       
  nvme format /dev/nvme0n1 --lbaf=1 --force

This will cause I/O errors because BLKRRPART ioctl() happened right after
the format command with same file descriptor opened in application (e.g., nvme-cli) like:

  fd = open("/dev/nvme0n1", O_RDONLY);

  nvme_format(fd, ...);
  if (ioctl(fd, BLKRRPART) < 0)
        ...

Errors:

We can see the Read command with Number of LBA(NLB) 0xffff(65535) which
was under-flowed because BLKRRPART operation requested request size based on i_blkbits of the block device which is 9 via buffer_head.

[dmesg-snip]

    [   10.771740] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [   10.780262] Buffer I/O error on dev nvme0n1, logical block 0, async page read

[event-snip]

    kworker/0:1H-56      [000] ....   913.456922: nvme_setup_cmd: nvme0: disk=nvme0n1, qid=1, cmdid=216, nsid=1, flags=0x0, meta=0x0, cmd=(nvme_cmd_read slba=0, len=65535, ctrl=0x0, dsmgmt=0, reftag=0)
     ksoftirqd/0-9       [000] .Ns.   916.566351: nvme_complete_rq: nvme0: disk=nvme0n1, qid=1, cmdid=216, res=0x0, retries=0, flags=0x0, status=0x4002

The patch below fixes the I/O errors by rejecting I/O requests from the
block layer with setting a flag to request_queue until the file descriptor re-opened to be updated by __blkdev_get(). This is based on the previous discussion [1].

Since V5:
- Rebased on for-next

Since V4:
- Rebased on block-5.11.
- Added Reviewed-by Tag from Christoph.

Since V3(RFC):
- Move flag from gendisk to request_queue for future clean-ups.

    (Christoph, [3])

Since V2(RFC):
- Cover letter with testcase and error logs attached. Removed un-related
changes: empty line. (Chaitanya, [2])
- Put blkdev with blkdev_put_no_open().

Since V1(RFC):
- Updated patch to reject I/O rather than updating i_blkbits of the block device's inode directly from driver. (Christoph, [1])

Minwoo Im (1):
block: reject I/O for same fd if block size changed

 block/blk-settings.c    |  3 +++
 block/partitions/core.c | 12 ++++++++++++
 fs/block_dev.c          |  8 ++++++++
 include/linux/blkdev.h  |  1 +
 4 files changed, 24 insertions(+)
Signature · 7 lines
2.17.1


_______________________________________________
Linux-nvme mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-nvme