From: Markus Elfring <Markus.Elfring@web.de>
To: Daejun Park <daejun7.park@samsung.com>,
linux-f2fs-devel@lists.sourceforge.net, Chao Yu <chao@kernel.org>,
Daeho Jeong <daehojeong@google.com>,
Jaegeuk Kim <jaegeuk@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Dongjin Kim <dongjin_.kim@samsung.com>,
Jaeyoon Choi <j_yoon.choi@samsung.com>,
Nayeon Kim <nayeoni.kim@samsung.com>,
Seokhwan Kim <sukka.kim@samsung.com>,
Siwoo Jung <siu.jung@samsung.com>,
Yonggil Song <yonggil.song@samsung.com>
Subject: Re: [PATCH] f2fs: fix null reference error when checking end of zone
Date: Thu, 4 Jul 2024 08:26:00 +0200 [thread overview]
Message-ID: <2121fd23-5cb8-493b-bee8-0c7d74bccfa9@web.de> (raw)
In-Reply-To: <20240704010121epcms2p4cff8b25d976d4a1b820ba18f1eb5aa90@epcms2p4>
> This patch fixes a potentially null pointer being accessed by
…
Please improve such a change description with imperative wordings.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc6#n94
How do you think about to use a summary phrase like
“Prevent null pointer dereference in is_end_zone_blkaddr()”?
Regards,
Markus
next prev parent reply other threads:[~2024-07-04 6:26 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 [this message]
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
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=2121fd23-5cb8-493b-bee8-0c7d74bccfa9@web.de \
--to=markus.elfring@web.de \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=daejun7.park@samsung.com \
--cc=dongjin_.kim@samsung.com \
--cc=j_yoon.choi@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 \
--cc=yonggil.song@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