From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Samuel Moelius <sam.moelius@trailofbits.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: validate dentry name length before lookup compares it
Date: Tue, 16 Jun 2026 02:50:06 +0000 [thread overview]
Message-ID: <178157820614.407856.1733629854453320542.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260603161127.17464-1-sam.moelius@trailofbits.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 3 Jun 2026 16:11:26 +0000 you wrote:
> The f2fs dentry lookup path can use the on-disk name length before
> checking that the name fits in the dentry filename area. A corrupted
> dentry can then make lookup read beyond the filename slots.
>
> The bounds check needs to happen before any comparison that consumes
> the name length from disk.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: validate dentry name length before lookup compares it
https://git.kernel.org/jaegeuk/f2fs/c/d6d43742e65d
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
prev parent reply other threads:[~2026-06-16 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 16:11 [f2fs-dev] [PATCH] f2fs: validate dentry name length before lookup compares it Samuel Moelius via Linux-f2fs-devel
2026-06-15 3:16 ` Chao Yu via Linux-f2fs-devel
2026-06-16 2:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=178157820614.407856.1733629854453320542.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=sam.moelius@trailofbits.com \
/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