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-f2fs-devel@lists.sourceforge.net,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to return -EFSCORRUPTED in f2fs_get_node_info() correctly
Date: Wed, 05 Aug 2026 21:20:52 +0000 [thread overview]
Message-ID: <178596485213.530543.10143463929977159330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260805122008.664576-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 5 Aug 2026 12:20:08 +0000 you wrote:
> Otherwise, it will cache wrong nat info in cache.
>
> Cc: stable@kernel.org
> Fixes: 3cb396a2c790 ("f2fs: fix to do sanity check on nat entry of quota inode")
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/node.c | 1 +
> 1 file changed, 1 insertion(+)
Here is the summary with links:
- [f2fs-dev] f2fs: fix to return -EFSCORRUPTED in f2fs_get_node_info() correctly
https://git.kernel.org/jaegeuk/f2fs/c/026d7aeadf27
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, stable@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to return -EFSCORRUPTED in f2fs_get_node_info() correctly
Date: Wed, 05 Aug 2026 21:20:52 +0000 [thread overview]
Message-ID: <178596485213.530543.10143463929977159330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260805122008.664576-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 5 Aug 2026 12:20:08 +0000 you wrote:
> Otherwise, it will cache wrong nat info in cache.
>
> Cc: stable@kernel.org
> Fixes: 3cb396a2c790 ("f2fs: fix to do sanity check on nat entry of quota inode")
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/node.c | 1 +
> 1 file changed, 1 insertion(+)
Here is the summary with links:
- [f2fs-dev] f2fs: fix to return -EFSCORRUPTED in f2fs_get_node_info() correctly
https://git.kernel.org/jaegeuk/f2fs/c/026d7aeadf27
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:[~2026-08-05 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 12:20 [f2fs-dev] [PATCH] f2fs: fix to return -EFSCORRUPTED in f2fs_get_node_info() correctly Chao Yu via Linux-f2fs-devel
2026-08-05 12:20 ` Chao Yu
2026-08-05 21:20 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-08-05 21:20 ` [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=178596485213.530543.10143463929977159330.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 \
--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.