From: Matthew Wilcox <willy@infradead.org>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] gfs2: Remove use of error flag in journal reads
Date: Wed, 20 Dec 2023 16:05:27 +0000 [thread overview]
Message-ID: <ZYMQx2070yb9Vkgs@casper.infradead.org> (raw)
In-Reply-To: <20231206195807.764344-1-willy@infradead.org>
On Wed, Dec 06, 2023 at 07:58:06PM +0000, Matthew Wilcox (Oracle) wrote:
> Conventionally we use the uptodate bit to signal whether a read
> encountered an error or not. Use folio_end_read() to set the uptodate
> bit on success. Also use filemap_set_wb_err() to communicate the errno
> instead of the more heavy-weight mapping_set_error().
Ping?
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> ---
> fs/gfs2/lops.c | 21 +++++++--------------
> 1 file changed, 7 insertions(+), 14 deletions(-)
>
> diff --git a/fs/gfs2/lops.c b/fs/gfs2/lops.c
> index 483f69807062..314ec2a70167 100644
> --- a/fs/gfs2/lops.c
> +++ b/fs/gfs2/lops.c
> @@ -391,22 +391,15 @@ static void gfs2_log_write_page(struct gfs2_sbd *sdp, struct page *page)
> * Simply unlock the pages in the bio. The main thread will wait on them and
> * process them in order as necessary.
> */
> -
> static void gfs2_end_log_read(struct bio *bio)
> {
> - struct page *page;
> - struct bio_vec *bvec;
> - struct bvec_iter_all iter_all;
> + int error = blk_status_to_errno(bio->bi_status);
> + struct folio_iter fi;
>
> - bio_for_each_segment_all(bvec, bio, iter_all) {
> - page = bvec->bv_page;
> - if (bio->bi_status) {
> - int err = blk_status_to_errno(bio->bi_status);
> -
> - SetPageError(page);
> - mapping_set_error(page->mapping, err);
> - }
> - unlock_page(page);
> + bio_for_each_folio_all(fi, bio) {
> + /* We're abusing wb_err to get the error to gfs2_find_jhead */
> + filemap_set_wb_err(fi.folio->mapping, error);
> + folio_end_read(fi.folio, !error);
> }
>
> bio_put(bio);
> @@ -475,7 +468,7 @@ static void gfs2_jhead_process_page(struct gfs2_jdesc *jd, unsigned long index,
> folio = filemap_get_folio(jd->jd_inode->i_mapping, index);
>
> folio_wait_locked(folio);
> - if (folio_test_error(folio))
> + if (!folio_test_uptodate(folio))
> *done = true;
>
> if (!*done)
> --
> 2.42.0
>
next prev parent reply other threads:[~2023-12-20 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 19:58 [PATCH] gfs2: Remove use of error flag in journal reads Matthew Wilcox (Oracle)
2023-12-20 16:05 ` Matthew Wilcox [this message]
2023-12-21 12:38 ` Andreas Gruenbacher
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=ZYMQx2070yb9Vkgs@casper.infradead.org \
--to=willy@infradead.org \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-fsdevel@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).