From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Haotian Li <lihaotian9@huawei.com>
Cc: virtio-fs@redhat.com, linfeilong@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Virtio-fs] [PATCH 2/3] virtiofsd: check whether lo_map_reserve returns NULL in, main func
Date: Wed, 11 Nov 2020 19:52:41 +0000 [thread overview]
Message-ID: <20201111195241.GO3232@work-vm> (raw)
In-Reply-To: <48887813-1c95-048c-6d10-48e3dd2bac71@huawei.com>
* Haotian Li (lihaotian9@huawei.com) wrote:
> In main func, func lo_map_reserve is called without NULL check.
> If reallocing new_elems fails in func lo_map_grow, the func
> lo_map_reserve may return NULL. We should check whether
> lo_map_reserve returns NULL before using it.
>
> Signed-off-by: Haotian Li <lihaotian9@huawei.com>
> Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
(I think the fuse_log will always fall through the default_log_func
becuase it's very early)
> ---
> tools/virtiofsd/passthrough_ll.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/tools/virtiofsd/passthrough_ll.c b/tools/virtiofsd/passthrough_ll.c
> index ec1008bceb..3e9bbc7a04 100644
> --- a/tools/virtiofsd/passthrough_ll.c
> +++ b/tools/virtiofsd/passthrough_ll.c
> @@ -3433,6 +3433,7 @@ int main(int argc, char *argv[])
> .proc_self_fd = -1,
> };
> struct lo_map_elem *root_elem;
> + struct lo_map_elem *reserve_elem;
> int ret = -1;
>
> /* Don't mask creation mode, kernel already did that */
> @@ -3452,8 +3453,17 @@ int main(int argc, char *argv[])
> * [1] Root inode
> */
> lo_map_init(&lo.ino_map);
> - lo_map_reserve(&lo.ino_map, 0)->in_use = false;
> + reserve_elem = lo_map_reserve(&lo.ino_map, 0);
> + if (!reserve_elem) {
> + fuse_log(FUSE_LOG_ERR, "failed to alloc reserve_elem.\n");
> + goto err_out1;
> + }
> + reserve_elem->in_use = false;
> root_elem = lo_map_reserve(&lo.ino_map, lo.root.fuse_ino);
> + if (!root_elem) {
> + fuse_log(FUSE_LOG_ERR, "failed to alloc root_elem.\n");
> + goto err_out1;
> + }
> root_elem->inode = &lo.root;
>
> lo_map_init(&lo.dirp_map);
> --
>
> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-11-11 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 1:04 [PATCH v3 0/3] virtiofsd: fix some accessing NULL pointer problem Haotian Li
2020-11-11 1:05 ` [PATCH 1/3] tools/virtiofsd/buffer.c: check whether buf is NULL in fuse_bufvec_advance func Haotian Li
2020-11-11 19:59 ` [Virtio-fs] " Dr. David Alan Gilbert
2020-11-11 1:09 ` [PATCH 2/3] virtiofsd: check whether lo_map_reserve returns NULL in, main func Haotian Li
2020-11-11 19:52 ` Dr. David Alan Gilbert [this message]
2020-11-11 1:10 ` [PATCH 3/3] virtiofsd: check whether strdup lo.source return NULL in " Haotian Li
2020-11-11 19:55 ` [Virtio-fs] " Dr. David Alan Gilbert
2020-11-12 16:25 ` [PATCH v3 0/3] virtiofsd: fix some accessing NULL pointer problem Dr. David Alan Gilbert
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=20201111195241.GO3232@work-vm \
--to=dgilbert@redhat.com \
--cc=lihaotian9@huawei.com \
--cc=linfeilong@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-fs@redhat.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;
as well as URLs for NNTP newsgroup(s).