From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Wenjie Qi <qwjhust@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, qiwenjie@xiaomi.com,
jaegeuk@kernel.org, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: limit recovery filename logging to stored length
Date: Wed, 05 Aug 2026 21:21:02 +0000 [thread overview]
Message-ID: <178596486263.530543.12202938187333968046.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260630082331.2757376-1-qiwenjie@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 30 Jun 2026 16:23:30 +0800 you wrote:
> F2FS stores recovery filenames as a length plus a fixed-size i_name
> buffer. The buffer is not NUL-terminated, but recover_inode() and
> recover_dentry() print it with %s.
>
> For a 255-byte filename, recovery logging can read past i_name into the
> following raw inode fields.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: limit recovery filename logging to stored length
https://git.kernel.org/jaegeuk/f2fs/c/01027b2fcb74
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: Wenjie Qi <qwjhust@gmail.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, stable@kernel.org,
qiwenjie@xiaomi.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: limit recovery filename logging to stored length
Date: Wed, 05 Aug 2026 21:21:02 +0000 [thread overview]
Message-ID: <178596486263.530543.12202938187333968046.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260630082331.2757376-1-qiwenjie@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 30 Jun 2026 16:23:30 +0800 you wrote:
> F2FS stores recovery filenames as a length plus a fixed-size i_name
> buffer. The buffer is not NUL-terminated, but recover_inode() and
> recover_dentry() print it with %s.
>
> For a 255-byte filename, recovery logging can read past i_name into the
> following raw inode fields.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: limit recovery filename logging to stored length
https://git.kernel.org/jaegeuk/f2fs/c/01027b2fcb74
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: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 8:23 [f2fs-dev] [PATCH] f2fs: limit recovery filename logging to stored length Wenjie Qi
2026-06-30 8:23 ` Wenjie Qi
2026-08-03 3:12 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-03 3:12 ` Chao Yu
2026-08-05 21:21 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-08-05 21:21 ` [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=178596486263.530543.12202938187333968046.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=qiwenjie@xiaomi.com \
--cc=qwjhust@gmail.com \
--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.