From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Mauricio Faria de Oliveira <mfo@canonical.com>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH] loop: fix I/O error on fsync() in detached loop devices
Date: Sat, 02 Jan 2021 02:13:53 -0300 [thread overview]
Message-ID: <87k0sv6hv2.fsf@collabora.com> (raw)
In-Reply-To: <20201231162845.1853347-1-mfo@canonical.com> (Mauricio Faria de Oliveira's message of "Thu, 31 Dec 2020 13:28:45 -0300")
Mauricio Faria de Oliveira <mfo@canonical.com> writes:
> There's an I/O error on fsync() in a detached loop device
> if it has been previously attached.
>
> The issue is write cache is enabled in the attach path in
> loop_configure() but it isn't disabled in the detach path;
> thus it remains enabled in the block device regardless of
> whether it is attached or not.
>
> Now fsync() can get an I/O request that will just be failed
> later in loop_queue_rq() as device's state is not 'Lo_bound'.
>
> So, disable write cache in the detach path.
>
> Test-case:
>
> # DEV=/dev/loop7
>
> # IMG=/tmp/image
> # truncate --size 1M $IMG
>
> # losetup $DEV $IMG
> # losetup -d $DEV
>
> Before:
>
> # strace -e fsync parted -s $DEV print 2>&1 | grep fsync
> fsync(3) = -1 EIO (Input/output error)
> Warning: Error fsyncing/closing /dev/loop7: Input/output error
> [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
>
> After:
>
> # strace -e fsync parted -s $DEV print 2>&1 | grep fsync
> fsync(3) = 0
>
> Signed-off-by: Mauricio Faria de Oliveira <mfo@canonical.com>
> Co-developed-by: Eric Desrochers <eric.desrochers@canonical.com>
> Signed-off-by: Eric Desrochers <eric.desrochers@canonical.com>
This sign-off chain is not sorted correctly. See Documentation/process/submitting-patches.rst.
Other than that, I think the fix makes sense.
Tested-by: Gabriel Krisman Bertazi <krisman@collabora.com>
> ---
> drivers/block/loop.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
> index e5ff328f0917..49517482e061 100644
> --- a/drivers/block/loop.c
> +++ b/drivers/block/loop.c
> @@ -1212,6 +1212,9 @@ static int __loop_clr_fd(struct loop_device *lo, bool release)
> goto out_unlock;
> }
>
> + if (!(lo->lo_flags & LO_FLAGS_READ_ONLY) && filp->f_op->fsync)
> + blk_queue_write_cache(lo->lo_queue, false, false);
> +
> /* freeze request queue during the transition */
> blk_mq_freeze_queue(lo->lo_queue);
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2021-01-02 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 16:28 [PATCH] loop: fix I/O error on fsync() in detached loop devices Mauricio Faria de Oliveira
2021-01-02 5:13 ` Gabriel Krisman Bertazi [this message]
2021-01-05 13:57 ` Mauricio Faria de Oliveira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0sv6hv2.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=mfo@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).