From: Jan Kara <jack@suse.cz>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>, Jan Kara <jack@suse.cz>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] block: Try to handle busy underlying device on discard
Date: Mon, 22 Feb 2021 12:59:53 +0100 [thread overview]
Message-ID: <20210222115953.GD19630@quack2.suse.cz> (raw)
In-Reply-To: <20210222094809.21775-1-jack@suse.cz>
On Mon 22-02-21 10:48:09, Jan Kara wrote:
> Commit 384d87ef2c95 ("block: Do not discard buffers under a mounted
> filesystem") made paths issuing discard or zeroout requests to the
> underlying device try to grab block device in exclusive mode. If that
> failed we returned EBUSY to userspace. This however caused unexpected
> fallout in userspace where e.g. FUSE filesystems issue discard requests
> from userspace daemons although the device is open exclusively by the
> kernel. Also shrinking of logical volume by LVM issues discard requests
> to a device which may be claimed exclusively because there's another LV
> on the same PV. So to avoid these userspace regressions, fall back to
> invalidate_inode_pages2_range() instead of returning EBUSY to userspace
> and return EBUSY only of that call fails as well (meaning that there's
> indeed someone using the particular device range we are trying to
> discard).
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=211167
> Fixes: 384d87ef2c95 ("block: Do not discard buffers under a mounted filesystem")
> CC: stable@vger.kernel.org
> Signed-off-by: Jan Kara <jack@suse.cz>
Before I forget: I'd like to add two tested by tags to give credit to
people who helped with testing.
Tested-by: Richard W.M. Jones <rjones@redhat.com>
Tested-by: Andreas Klauer <Andreas.Klauer@metamorpher.de>
Honza
> ---
> fs/block_dev.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/fs/block_dev.c b/fs/block_dev.c
> index 235b5042672e..c33151020bcd 100644
> --- a/fs/block_dev.c
> +++ b/fs/block_dev.c
> @@ -118,13 +118,22 @@ int truncate_bdev_range(struct block_device *bdev, fmode_t mode,
> if (!(mode & FMODE_EXCL)) {
> int err = bd_prepare_to_claim(bdev, truncate_bdev_range);
> if (err)
> - return err;
> + goto invalidate;
> }
>
> truncate_inode_pages_range(bdev->bd_inode->i_mapping, lstart, lend);
> if (!(mode & FMODE_EXCL))
> bd_abort_claiming(bdev, truncate_bdev_range);
> return 0;
> +
> +invalidate:
> + /*
> + * Someone else has handle exclusively open. Try invalidating instead.
> + * The 'end' argument is inclusive so the rounding is safe.
> + */
> + return invalidate_inode_pages2_range(bdev->bd_inode->i_mapping,
> + lstart >> PAGE_SHIFT,
> + lend >> PAGE_SHIFT);
> }
> EXPORT_SYMBOL(truncate_bdev_range);
>
> --
> 2.26.2
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2021-02-22 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 9:48 [PATCH v2] block: Try to handle busy underlying device on discard Jan Kara
2021-02-22 11:59 ` Jan Kara [this message]
2021-03-04 12:02 ` Jan Kara
2021-03-05 13:12 ` Christoph Hellwig
2021-03-05 18:27 ` Jens Axboe
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=20210222115953.GD19630@quack2.suse.cz \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).