From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, hch@lst.de,
linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 5/5] xfs: Pass a page to xfs_finish_page_writeback
Date: Wed, 18 Sep 2019 14:32:21 -0700 [thread overview]
Message-ID: <20190918213221.GF2229799@magnolia> (raw)
In-Reply-To: <20190821003039.12555-6-willy@infradead.org>
On Tue, Aug 20, 2019 at 05:30:39PM -0700, Matthew Wilcox wrote:
> From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
>
> The only part of the bvec we were accessing was the bv_page, so just
> pass that instead of the whole bvec.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Seems fine but same caveats about tree churn as the previous patch.
--D
> ---
> fs/xfs/xfs_aops.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index 1a26e9ca626b..edcb4797fcc2 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_aops.c
> @@ -58,21 +58,21 @@ xfs_find_daxdev_for_inode(
> static void
> xfs_finish_page_writeback(
> struct inode *inode,
> - struct bio_vec *bvec,
> + struct page *page,
> int error)
> {
> - struct iomap_page *iop = to_iomap_page(bvec->bv_page);
> + struct iomap_page *iop = to_iomap_page(page);
>
> if (error) {
> - SetPageError(bvec->bv_page);
> + SetPageError(page);
> mapping_set_error(inode->i_mapping, -EIO);
> }
>
> - ASSERT(iop || i_blocks_per_page(inode, bvec->bv_page) <= 1);
> + ASSERT(iop || i_blocks_per_page(inode, page) <= 1);
> ASSERT(!iop || atomic_read(&iop->write_count) > 0);
>
> if (!iop || atomic_dec_and_test(&iop->write_count))
> - end_page_writeback(bvec->bv_page);
> + end_page_writeback(page);
> }
>
> /*
> @@ -106,7 +106,7 @@ xfs_destroy_ioend(
>
> /* walk each page on bio, ending page IO on them */
> bio_for_each_segment_all(bvec, bio, iter_all)
> - xfs_finish_page_writeback(inode, bvec, error);
> + xfs_finish_page_writeback(inode, bvec->bv_page, error);
> bio_put(bio);
> }
>
> --
> 2.23.0.rc1
>
prev parent reply other threads:[~2019-09-18 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 0:30 [PATCH v2 0/5] iomap & xfs support for large pages Matthew Wilcox
2019-08-21 0:30 ` [PATCH v2 1/5] fs: Introduce i_blocks_per_page Matthew Wilcox
2019-08-23 12:26 ` kbuild test robot
2019-09-18 21:14 ` Darrick J. Wong
2019-09-18 23:48 ` Matthew Wilcox
2019-08-21 0:30 ` [PATCH v2 2/5] mm: Add file_offset_of_ helpers Matthew Wilcox
2019-08-23 12:49 ` kbuild test robot
2019-08-24 11:48 ` kbuild test robot
2019-08-24 15:28 ` Matthew Wilcox
2019-09-18 21:17 ` Darrick J. Wong
2019-09-18 23:49 ` Matthew Wilcox
2019-09-19 0:04 ` Darrick J. Wong
2019-08-21 0:30 ` [PATCH v2 3/5] iomap: Support large pages Matthew Wilcox
2019-08-23 12:48 ` kbuild test robot
2019-09-18 21:29 ` Darrick J. Wong
2019-08-21 0:30 ` [PATCH v2 4/5] xfs: " Matthew Wilcox
2019-09-18 21:31 ` Darrick J. Wong
2019-08-21 0:30 ` [PATCH v2 5/5] xfs: Pass a page to xfs_finish_page_writeback Matthew Wilcox
2019-09-18 21:32 ` Darrick J. Wong [this message]
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=20190918213221.GF2229799@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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).