From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, butterflyhuangxx@gmail.com
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to avoid NULL pointer dereference f2fs_write_end_io()
Date: Tue, 30 May 2023 23:40:24 +0000 [thread overview]
Message-ID: <168549002416.8773.766514446956426834.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230523061725.650692-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 23 May 2023 14:17:25 +0800 you wrote:
> butt3rflyh4ck reports a bug as below:
>
> When a thread always calls F2FS_IOC_RESIZE_FS to resize fs, if resize fs is
> failed, f2fs kernel thread would invoke callback function to update f2fs io
> info, it would call f2fs_write_end_io and may trigger null-ptr-deref in
> NODE_MAPPING.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to avoid NULL pointer dereference f2fs_write_end_io()
https://git.kernel.org/jaegeuk/f2fs/c/9318465d0e82
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:[~2023-05-30 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 6:17 [f2fs-dev] [PATCH v2] f2fs: fix to avoid NULL pointer dereference f2fs_write_end_io() Chao Yu
2023-05-30 23:40 ` 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=168549002416.8773.766514446956426834.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=butterflyhuangxx@gmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).