From: Bill O'Donnell <billodo@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/3] vfs: fix page locking deadlocks when deduping files
Date: Fri, 9 Aug 2019 07:35:03 -0500 [thread overview]
Message-ID: <20190809123503.GA26462@redhat.com> (raw)
In-Reply-To: <156527561641.1960675.7113883901730327475.stgit@magnolia>
On Thu, Aug 08, 2019 at 07:46:56AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> When dedupe wants to use the page cache to compare parts of two files
> for dedupe, we must be very careful to handle locking correctly. The
> current code doesn't do this. It must lock and unlock the page only
> once if the two pages are the same, since the overlapping range check
> doesn't catch this when blocksize < pagesize. If the pages are distinct
> but from the same file, we must observe page locking order and lock them
> in order of increasing offset to avoid clashing with writeback locking.
>
> Fixes: 876bec6f9bbfcb3 ("vfs: refactor clone/dedupe_file_range common functions")
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Bill O'Donnell <billodo@redhat.com>
> ---
> fs/read_write.c | 36 ++++++++++++++++++++++++++++--------
> 1 file changed, 28 insertions(+), 8 deletions(-)
>
>
> diff --git a/fs/read_write.c b/fs/read_write.c
> index 1f5088dec566..4dbdccffa59e 100644
> --- a/fs/read_write.c
> +++ b/fs/read_write.c
> @@ -1811,10 +1811,7 @@ static int generic_remap_check_len(struct inode *inode_in,
> return (remap_flags & REMAP_FILE_DEDUP) ? -EBADE : -EINVAL;
> }
>
> -/*
> - * Read a page's worth of file data into the page cache. Return the page
> - * locked.
> - */
> +/* Read a page's worth of file data into the page cache. */
> static struct page *vfs_dedupe_get_page(struct inode *inode, loff_t offset)
> {
> struct page *page;
> @@ -1826,10 +1823,32 @@ static struct page *vfs_dedupe_get_page(struct inode *inode, loff_t offset)
> put_page(page);
> return ERR_PTR(-EIO);
> }
> - lock_page(page);
> return page;
> }
>
> +/*
> + * Lock two pages, ensuring that we lock in offset order if the pages are from
> + * the same file.
> + */
> +static void vfs_lock_two_pages(struct page *page1, struct page *page2)
> +{
> + /* Always lock in order of increasing index. */
> + if (page1->index > page2->index)
> + swap(page1, page2);
> +
> + lock_page(page1);
> + if (page1 != page2)
> + lock_page(page2);
> +}
> +
> +/* Unlock two pages, being careful not to unlock the same page twice. */
> +static void vfs_unlock_two_pages(struct page *page1, struct page *page2)
> +{
> + unlock_page(page1);
> + if (page1 != page2)
> + unlock_page(page2);
> +}
> +
> /*
> * Compare extents of two files to see if they are the same.
> * Caller must have locked both inodes to prevent write races.
> @@ -1867,10 +1886,12 @@ static int vfs_dedupe_file_range_compare(struct inode *src, loff_t srcoff,
> dest_page = vfs_dedupe_get_page(dest, destoff);
> if (IS_ERR(dest_page)) {
> error = PTR_ERR(dest_page);
> - unlock_page(src_page);
> put_page(src_page);
> goto out_error;
> }
> +
> + vfs_lock_two_pages(src_page, dest_page);
> +
> src_addr = kmap_atomic(src_page);
> dest_addr = kmap_atomic(dest_page);
>
> @@ -1882,8 +1903,7 @@ static int vfs_dedupe_file_range_compare(struct inode *src, loff_t srcoff,
>
> kunmap_atomic(dest_addr);
> kunmap_atomic(src_addr);
> - unlock_page(dest_page);
> - unlock_page(src_page);
> + vfs_unlock_two_pages(src_page, dest_page);
> put_page(dest_page);
> put_page(src_page);
>
>
next prev parent reply other threads:[~2019-08-09 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 14:46 [PATCH 0/3] xfs: various fixes for 5.3 Darrick J. Wong
2019-08-08 14:46 ` [PATCH 1/3] vfs: fix page locking deadlocks when deduping files Darrick J. Wong
2019-08-09 12:35 ` Bill O'Donnell [this message]
2019-08-11 23:09 ` Dave Chinner
2019-08-08 14:47 ` [PATCH 2/3] xfs: remove more ondisk directory corruption asserts Darrick J. Wong
2019-08-08 16:05 ` Bill O'Donnell
2019-08-08 14:47 ` [PATCH 3/3] xfs: don't crash on null attr fork xfs_bmapi_read Darrick J. Wong
2019-08-08 14:51 ` Bill O'Donnell
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=20190809123503.GA26462@redhat.com \
--to=billodo@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.