From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: clear PageError on the read path
Date: Fri, 28 Sep 2018 19:58:46 +0800 [thread overview]
Message-ID: <04bbaf3a-e1ec-a5ae-a664-68d1299aaeb6@kernel.org> (raw)
In-Reply-To: <20180926014617.12369-1-jaegeuk@kernel.org>
On 2018-9-26 9:46, Jaegeuk Kim wrote:
> When running fault injection test, I hit somewhat wrong behavior in f2fs_gc ->
> gc_data_segment():
>
> 0. fault injection generated some PageError'ed pages
>
> 1. gc_data_segment
> -> f2fs_get_read_data_page(REQ_RAHEAD)
>
> 2. move_data_page
> -> f2fs_get_lock_data_page()
> -> f2f_get_read_data_page()
> -> f2fs_submit_page_read()
> -> submit_bio(READ)
> -> return EIO due to PageError
> -> fail to move data
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/data.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 41102c227eee..cb3ebcae0398 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -77,7 +77,8 @@ static void __read_end_io(struct bio *bio)
> /* PG_error was set if any post_read step failed */
> if (bio->bi_status || PageError(page)) {
> ClearPageUptodate(page);
> - SetPageError(page);
> + /* will re-read again later */
> + ClearPageError(page);
> } else {
> SetPageUptodate(page);
How about:
if (PaegeError(page))
ClearPageError(page);
if (bio->bi_status) {
ClearPageUptodate(page);
SetPageError(page);
} else {
SetPageUptodate(page);
ClearPageError(page);
}
So that below codes are not needed.
Thanks,
> }
> @@ -591,6 +592,7 @@ static int f2fs_submit_page_read(struct inode *inode, struct page *page,
> bio_put(bio);
> return -EFAULT;
> }
> + ClearPageError(page);
> __submit_bio(F2FS_I_SB(inode), bio, DATA);
> return 0;
> }
> @@ -1571,6 +1573,7 @@ static int f2fs_mpage_readpages(struct address_space *mapping,
> if (bio_add_page(bio, page, blocksize, 0) < blocksize)
> goto submit_and_realloc;
>
> + ClearPageError(page);
> last_block_in_bio = block_nr;
> goto next_page;
> set_error_page:
>
prev parent reply other threads:[~2018-09-28 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 1:46 [PATCH 1/2] f2fs: clear PageError on the read path Jaegeuk Kim
2018-09-26 1:46 ` [PATCH 2/2] f2fs: return correct errno in f2fs_gc Jaegeuk Kim
2018-09-28 10:45 ` [f2fs-dev] " Chao Yu
2018-09-28 11:58 ` Chao Yu [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=04bbaf3a-e1ec-a5ae-a664-68d1299aaeb6@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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).