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 2/2 v3] f2fs: avoid f2fs_bug_on if f2fs_get_meta_page_nofail got EIO
Date: Thu, 27 Sep 2018 20:09:57 +0800 [thread overview]
Message-ID: <0c036757-5200-e952-e814-d07aa50af90f@kernel.org> (raw)
In-Reply-To: <20180920214804.GF35918@jaegeuk-macbookpro.roam.corp.google.com>
On 2018-9-21 5:48, Jaegeuk Kim wrote:
> This patch avoids BUG_ON when f2fs_get_meta_page_nofail got EIO during
> xfstests/generic/475.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
next prev parent reply other threads:[~2018-09-27 12:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 2:18 [PATCH 1/2] f2fs: report ENOENT correct in f2fs_rename Jaegeuk Kim
2018-09-18 2:18 ` [PATCH 2/2] f2fs: avoid f2fs_bug_on if f2fs_get_meta_page_nofail got EIO Jaegeuk Kim
2018-09-18 13:16 ` [f2fs-dev] " Chao Yu
2018-09-18 17:55 ` Jaegeuk Kim
2018-09-18 17:56 ` [PATCH 2/2 v2] " Jaegeuk Kim
2018-09-19 1:45 ` [f2fs-dev] " Chao Yu
2018-09-19 22:47 ` Jaegeuk Kim
2018-09-20 6:07 ` Chao Yu
2018-09-20 21:46 ` Jaegeuk Kim
2018-09-21 1:30 ` Chao Yu
2018-09-26 0:18 ` Jaegeuk Kim
2018-09-26 1:10 ` Chao Yu
2018-09-26 8:31 ` Chao Yu
2018-09-26 19:49 ` Jaegeuk Kim
2018-09-27 1:14 ` Chao Yu
2018-09-27 4:58 ` Jaegeuk Kim
2018-09-27 5:45 ` Chao Yu
2018-09-20 21:48 ` [f2fs-dev] [PATCH 2/2 v3] " Jaegeuk Kim
2018-09-27 12:09 ` Chao Yu [this message]
2018-09-18 12:47 ` [f2fs-dev] [PATCH 1/2] f2fs: report ENOENT correct in f2fs_rename Chao Yu
2018-09-18 17:59 ` Jaegeuk Kim
2018-09-19 1:48 ` Chao Yu
2018-09-19 0:47 ` Sahitya Tummala
2018-09-19 22:50 ` [PATCH 1/2 v2] " Jaegeuk Kim
2018-09-20 6:14 ` [f2fs-dev] " Chao Yu
2018-09-20 21:35 ` [f2fs-dev] [PATCH 1/2 v3] " Jaegeuk Kim
2018-09-21 1:31 ` Chao Yu
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=0c036757-5200-e952-e814-d07aa50af90f@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).