From: Jeff Layton <jlayton@kernel.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>,
idryomov@gmail.com, davem@davemloft.net, kuba@kernel.org
Cc: ceph-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libceph, ceph: potential dereference of null pointer
Date: Thu, 09 Dec 2021 06:20:40 -0500 [thread overview]
Message-ID: <2a79206d3472b279079fbef5c9507f8805061c47.camel@kernel.org> (raw)
In-Reply-To: <20211209025038.2028112-1-jiasheng@iscas.ac.cn>
On Thu, 2021-12-09 at 10:50 +0800, Jiasheng Jiang wrote:
> The return value of kzalloc() needs to be checked.
> To avoid use of null pointer in case of the failure of alloc.
>
> Fixes: 3d14c5d2b6e1 ("ceph: factor out libceph from Ceph file system")
> Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
> ---
> net/ceph/osd_client.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/net/ceph/osd_client.c b/net/ceph/osd_client.c
> index ff8624a7c964..3203e8a34370 100644
> --- a/net/ceph/osd_client.c
> +++ b/net/ceph/osd_client.c
> @@ -1234,6 +1234,8 @@ static struct ceph_osd *create_osd(struct ceph_osd_client *osdc, int onum)
> WARN_ON(onum == CEPH_HOMELESS_OSD);
>
> osd = kzalloc(sizeof(*osd), GFP_NOIO | __GFP_NOFAIL);
> + if (!osd)
> + return NULL;
> osd_init(osd);
> osd->o_osdc = osdc;
> osd->o_osd = onum;
__GFP_NOFAIL should ensure that it never returns NULL, right?
Also, if you're going to fix this up to handle that error then you
probably also need to fix lookup_create_osd to handle a NULL return from
create_osd as well.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2021-12-09 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 2:50 [PATCH] libceph, ceph: potential dereference of null pointer Jiasheng Jiang
2021-12-09 11:20 ` Jeff Layton [this message]
2021-12-09 12:59 ` Xiubo Li
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=2a79206d3472b279079fbef5c9507f8805061c47.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=idryomov@gmail.com \
--cc=jiasheng@iscas.ac.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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