From: Haotian Li <lihaotian9@huawei.com>
To: <qemu-devel@nongnu.org>, <virtio-fs@redhat.com>
Cc: linfeilong@huawei.com, liuzhiqiang26@huawei.com
Subject: [PATCH 0/2] virtiofsd: fix some accessing NULL pointer problem
Date: Tue, 10 Nov 2020 09:09:12 +0800 [thread overview]
Message-ID: <eeb2fd1d-a53d-eae6-4727-7f1a6b20ac9e@huawei.com> (raw)
Hi,
We find some potential NULL pointer bugs on tools/virtiofsd.
Two patches are made to fix them.
Haotian Li (2):
tools/virtiofsd/buffer.c: check whether buf is NULL in
fuse_bufvec_advance func
virtiofsd/passthrough_ll.c: check whether lo_map_reserve returns NULL
in main func
tools/virtiofsd/buffer.c | 3 +++
tools/virtiofsd/passthrough_ll.c | 8 +++++++-
2 files changed, 10 insertions(+), 1 deletion(-)
next reply other threads:[~2020-11-10 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 1:09 Haotian Li [this message]
2020-11-10 1:10 ` [PATCH 1/2] tools/virtiofsd/buffer.c: check whether buf is NULL in fuse_bufvec_advance func Haotian Li
2020-11-10 1:11 ` [PATCH 2/2] virtiofsd: check whether lo_map_reserve returns NULL in main func Haotian Li
2020-11-10 1:18 ` [PATCH 0/2] virtiofsd: fix some accessing NULL pointer problem no-reply
2020-11-10 6:01 ` Haotian 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=eeb2fd1d-a53d-eae6-4727-7f1a6b20ac9e@huawei.com \
--to=lihaotian9@huawei.com \
--cc=linfeilong@huawei.com \
--cc=liuzhiqiang26@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).