From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix false alarm on invalid block address
Date: Thu, 25 Apr 2024 09:23:58 +0800 [thread overview]
Message-ID: <7bb95d2c-be0d-488b-9f0c-23167d84e057@kernel.org> (raw)
In-Reply-To: <20240424173548.1515606-1-jaegeuk@kernel.org>
On 2024/4/25 1:35, Jaegeuk Kim wrote:
> f2fs_ra_meta_pages can try to read ahead on invalid block address which is
> not the corruption case.
>
> Cc: <stable@kernel.org> # v6.9+
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=218770
> Fixes: 31f85ccc84b8 ("f2fs: unify the error handling of f2fs_is_valid_blkaddr")
> 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
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix false alarm on invalid block address
Date: Thu, 25 Apr 2024 09:23:58 +0800 [thread overview]
Message-ID: <7bb95d2c-be0d-488b-9f0c-23167d84e057@kernel.org> (raw)
In-Reply-To: <20240424173548.1515606-1-jaegeuk@kernel.org>
On 2024/4/25 1:35, Jaegeuk Kim wrote:
> f2fs_ra_meta_pages can try to read ahead on invalid block address which is
> not the corruption case.
>
> Cc: <stable@kernel.org> # v6.9+
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=218770
> Fixes: 31f85ccc84b8 ("f2fs: unify the error handling of f2fs_is_valid_blkaddr")
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-04-25 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 17:35 [f2fs-dev] [PATCH] f2fs: fix false alarm on invalid block address Jaegeuk Kim
2024-04-24 17:35 ` Jaegeuk Kim
2024-04-25 1:23 ` Chao Yu [this message]
2024-04-25 1:23 ` [f2fs-dev] " Chao Yu
2024-04-25 15:40 ` patchwork-bot+f2fs
2024-04-25 15:40 ` patchwork-bot+f2fs
-- strict thread matches above, loose matches on Subject: below --
2024-05-20 22:02 Jaegeuk Kim
2024-05-23 17:44 ` Jaegeuk Kim
2024-05-23 17:46 ` Jaegeuk Kim
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=7bb95d2c-be0d-488b-9f0c-23167d84e057@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.