From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to detect potential corrupted nid in free_nid_list
Date: Fri, 15 Aug 2025 16:40:15 +0000 [thread overview]
Message-ID: <175527601523.1161945.903553977374794343.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250807024431.3805293-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 7 Aug 2025 10:44:31 +0800 you wrote:
> As reported, on-disk footer.ino and footer.nid is the same and
> out-of-range, let's add sanity check on f2fs_alloc_nid() to detect
> any potential corruption in free_nid_list.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/node.c | 17 ++++++++++++++++-
> include/linux/f2fs_fs.h | 1 +
> 2 files changed, 17 insertions(+), 1 deletion(-)
Here is the summary with links:
- [f2fs-dev] f2fs: fix to detect potential corrupted nid in free_nid_list
https://git.kernel.org/jaegeuk/f2fs/c/3e7be92e436e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
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: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to detect potential corrupted nid in free_nid_list
Date: Fri, 15 Aug 2025 16:40:15 +0000 [thread overview]
Message-ID: <175527601523.1161945.903553977374794343.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250807024431.3805293-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 7 Aug 2025 10:44:31 +0800 you wrote:
> As reported, on-disk footer.ino and footer.nid is the same and
> out-of-range, let's add sanity check on f2fs_alloc_nid() to detect
> any potential corruption in free_nid_list.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/node.c | 17 ++++++++++++++++-
> include/linux/f2fs_fs.h | 1 +
> 2 files changed, 17 insertions(+), 1 deletion(-)
Here is the summary with links:
- [f2fs-dev] f2fs: fix to detect potential corrupted nid in free_nid_list
https://git.kernel.org/jaegeuk/f2fs/c/3e7be92e436e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-08-15 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 2:44 [f2fs-dev] [PATCH] f2fs: fix to detect potential corrupted nid in free_nid_list Chao Yu via Linux-f2fs-devel
2025-08-07 2:44 ` Chao Yu
2025-08-15 16:40 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-08-15 16:40 ` [f2fs-dev] " patchwork-bot+f2fs
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=175527601523.1161945.903553977374794343.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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.