From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] fsck.f2fs: don't call dev_fill w/ null buffer
Date: Wed, 14 Aug 2024 18:07:51 +0800 [thread overview]
Message-ID: <dcc14b9e-aeb0-4718-a60d-b40719ee6543@kernel.org> (raw)
In-Reply-To: <20240808233248.323318-1-jaegeuk@kernel.org>
On 2024/8/9 7:32, Jaegeuk Kim wrote:
> It'll crach fsck.f2fs. Even, let's keep the write pointers and just finish it.
>
> 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:[~2024-08-14 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 23:32 [f2fs-dev] [PATCH] fsck.f2fs: don't call dev_fill w/ null buffer Jaegeuk Kim
2024-08-12 18:41 ` Daeho Jeong
2024-08-12 19:56 ` Jaegeuk Kim
2024-08-13 17:36 ` Daeho Jeong
2024-08-14 10:07 ` 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=dcc14b9e-aeb0-4718-a60d-b40719ee6543@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).