From: patchwork-bot+f2fs@kernel.org
To: Daejun Park <daejun7.park@samsung.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, daehojeong@google.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, nayeoni.kim@samsung.com,
siu.jung@samsung.com, sukka.kim@samsung.com,
dongjin_.kim@samsung.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix null reference error when checking end of zone
Date: Mon, 15 Jul 2024 14:40:32 +0000 [thread overview]
Message-ID: <172105443215.17443.11491545195159801035.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240704010121epcms2p4cff8b25d976d4a1b820ba18f1eb5aa90@epcms2p4>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 04 Jul 2024 10:01:21 +0900 you wrote:
> This patch fixes a potentially null pointer being accessed by
> is_end_zone_blkaddr() that checks the last block of a zone
> when f2fs is mounted as a single device.
>
> Fixes: e067dc3c6b9c ("f2fs: maintain six open zones for zoned devices")
> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix null reference error when checking end of zone
https://git.kernel.org/jaegeuk/f2fs/c/c82bc1ab2a8a
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:[~2024-07-15 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240704010121epcms2p4cff8b25d976d4a1b820ba18f1eb5aa90@epcms2p4>
2024-07-04 1:01 ` [PATCH] f2fs: fix null reference error when checking end of zone Daejun Park
2024-07-04 6:26 ` Markus Elfring
2024-07-04 7:15 ` Chao Yu
2024-07-04 7:55 ` Daejun Park
2024-07-04 9:32 ` (2) " Chao Yu
2024-07-09 22:20 ` [f2fs-dev] " Daeho Jeong
2024-07-15 14: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=172105443215.17443.11491545195159801035.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=daejun7.park@samsung.com \
--cc=dongjin_.kim@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nayeoni.kim@samsung.com \
--cc=siu.jung@samsung.com \
--cc=sukka.kim@samsung.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