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,
linux-kernel@vger.kernel.org, leocstone@gmail.com,
syzbot+b01a36acd7007e273a83@syzkaller.appspotmail.com
Subject: Re: [f2fs-dev] [PATCH v3 RESEND] f2fs: add check for deleted inode
Date: Wed, 12 Feb 2025 03:00:39 +0000 [thread overview]
Message-ID: <173932923927.82998.635511827116437277.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250211071725.457343-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 11 Feb 2025 15:17:25 +0800 you wrote:
> From: Leo Stone <leocstone@gmail.com>
>
> The syzbot reproducer mounts a f2fs image, then tries to unlink an
> existing file. However, the unlinked file already has a link count of 0
> when it is read for the first time in do_read_inode().
>
> Add a check to sanity_check_inode() for i_nlink == 0.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,RESEND] f2fs: add check for deleted inode
https://git.kernel.org/jaegeuk/f2fs/c/6e3019906688
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,
syzbot+b01a36acd7007e273a83@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, leocstone@gmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 RESEND] f2fs: add check for deleted inode
Date: Wed, 12 Feb 2025 03:00:39 +0000 [thread overview]
Message-ID: <173932923927.82998.635511827116437277.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250211071725.457343-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 11 Feb 2025 15:17:25 +0800 you wrote:
> From: Leo Stone <leocstone@gmail.com>
>
> The syzbot reproducer mounts a f2fs image, then tries to unlink an
> existing file. However, the unlinked file already has a link count of 0
> when it is read for the first time in do_read_inode().
>
> Add a check to sanity_check_inode() for i_nlink == 0.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,RESEND] f2fs: add check for deleted inode
https://git.kernel.org/jaegeuk/f2fs/c/6e3019906688
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-02-12 3:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 7:17 [f2fs-dev] [PATCH v3 RESEND] f2fs: add check for deleted inode Chao Yu via Linux-f2fs-devel
2025-02-11 7:17 ` Chao Yu
2025-02-12 3:00 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-02-12 3:00 ` [f2fs-dev] " patchwork-bot+f2fs
2025-02-12 3:24 ` Jaegeuk Kim via Linux-f2fs-devel
2025-02-12 3:24 ` Jaegeuk Kim
2025-02-12 3:38 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-02-12 3:38 ` Chao Yu
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=173932923927.82998.635511827116437277.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=leocstone@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=syzbot+b01a36acd7007e273a83@syzkaller.appspotmail.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 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.