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: fix wrong condition check when failing metapage read
Date: Sun, 17 Apr 2022 14:36:41 +0800 [thread overview]
Message-ID: <38535431-906e-a61d-4feb-156df9585bdf@kernel.org> (raw)
In-Reply-To: <20220411212141.1775589-1-jaegeuk@kernel.org>
On 2022/4/12 5:21, Jaegeuk Kim wrote:
> This patch fixes wrong initialization.
>
> Fixes: 50c63009f6ab ("f2fs: avoid an infinite loop in f2fs_sync_dirty_inodes")
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2022-04-17 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 21:21 [f2fs-dev] [PATCH 1/2] f2fs: fix wrong condition check when failing metapage read Jaegeuk Kim
2022-04-11 21:21 ` [f2fs-dev] [PATCH 2/2] f2fs: avoid infinite loop to flush node pages Jaegeuk Kim
2022-04-14 22:27 ` [f2fs-dev] [PATCH 2/2 v2] " Jaegeuk Kim
2022-04-17 6:41 ` Chao Yu
2022-04-19 23:00 ` [f2fs-dev] [PATCH 2/2 v3] " Jaegeuk Kim
2022-04-17 6:36 ` 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=38535431-906e-a61d-4feb-156df9585bdf@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).