From: patchwork-bot+f2fs@kernel.org
To: Nikola Z. Ivanov <zlatistiv@gmail.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
david.hunter.linux@gmail.com, linux-kernel@vger.kernel.org,
khalid@kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH v4 0/2] f2fs: Add sanity checks before unlinking and loading inodes
Date: Tue, 11 Nov 2025 22:50:22 +0000 [thread overview]
Message-ID: <176290142299.3596344.2753827119628915512.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1762339963.git.zlatistiv@gmail.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 5 Nov 2025 13:09:41 +0200 you wrote:
> This series is provoked by syzbot warnings caused by corrupted directory
> inode with i_nlink == 1 that passes the initial sanity check which will
> only mark the filesystem as corrupted in case i_nlink == 0.
>
> Tests:
> - fio/fsmark parallel create/unlink on VM with f2fs root filesystem.
> - syzbot
>
> [...]
Here is the summary with links:
- [f2fs-dev,v4,1/2] f2fs: Rename f2fs_unlink exit label
https://git.kernel.org/jaegeuk/f2fs/c/7b4827ce2d2a
- [f2fs-dev,v4,2/2] f2fs: Add sanity checks before unlinking and loading inodes
https://git.kernel.org/jaegeuk/f2fs/c/d43f8de77d6c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-11 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 11:09 [PATCH v4 0/2] f2fs: Add sanity checks before unlinking and loading inodes Nikola Z. Ivanov
2025-11-05 11:09 ` [PATCH v4 1/2] f2fs: Rename f2fs_unlink exit label Nikola Z. Ivanov
2025-11-05 11:14 ` Chao Yu
2025-11-05 11:09 ` [PATCH v4 2/2] f2fs: Add sanity checks before unlinking and loading inodes Nikola Z. Ivanov
2025-11-05 11:14 ` Chao Yu
2025-11-11 22:50 ` patchwork-bot+f2fs [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=176290142299.3596344.2753827119628915512.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=david.hunter.linux@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=khalid@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@kernel.org \
--cc=zlatistiv@gmail.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