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, liuzhiqiang26@huawei.com Subject: Re: [PATCH v3 0/3] virtiofsd: fix some accessing NULL pointer problem Date: Thu, 12 Nov 2020 16:25:50 +0000 [thread overview] Message-ID: <20201112162550.GH13424@work-vm> (raw) In-Reply-To: <3477d902-ace9-1aa1-531a-9d20d6e93a05@huawei.com> * Haotian Li (lihaotian9@huawei.com) wrote: > Hi, > We find some potential NULL pointer bugs on tools/virtiofsd. > Three patches are made to fix them Queued > Haotian Li (3): > tools/virtiofsd/buffer.c: check whether buf is NULL in > fuse_bufvec_advance func > virtiofsd: check whether lo_map_reserve returns NULL in main func > virtiofsd: check whether strdup lo.source return NULL in main func. > > tools/virtiofsd/buffer.c | 4 ++++ > tools/virtiofsd/passthrough_ll.c | 16 +++++++++++++++- > 2 files changed, 19 insertions(+), 1 deletion(-) > > -- > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
WARNING: multiple messages have this Message-ID (diff)
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 v3 0/3] virtiofsd: fix some accessing NULL pointer problem Date: Thu, 12 Nov 2020 16:25:50 +0000 [thread overview] Message-ID: <20201112162550.GH13424@work-vm> (raw) In-Reply-To: <3477d902-ace9-1aa1-531a-9d20d6e93a05@huawei.com> * Haotian Li (lihaotian9@huawei.com) wrote: > Hi, > We find some potential NULL pointer bugs on tools/virtiofsd. > Three patches are made to fix them Queued > Haotian Li (3): > tools/virtiofsd/buffer.c: check whether buf is NULL in > fuse_bufvec_advance func > virtiofsd: check whether lo_map_reserve returns NULL in main func > virtiofsd: check whether strdup lo.source return NULL in main func. > > tools/virtiofsd/buffer.c | 4 ++++ > tools/virtiofsd/passthrough_ll.c | 16 +++++++++++++++- > 2 files changed, 19 insertions(+), 1 deletion(-) > > -- > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-11-12 16:26 UTC|newest] Thread overview: 13+ 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:04 ` [Virtio-fs] " 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 1:05 ` [Virtio-fs] " Haotian Li 2020-11-11 19:59 ` 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 1:09 ` [Virtio-fs] " Haotian Li 2020-11-11 19:52 ` Dr. David Alan Gilbert 2020-11-11 1:10 ` [PATCH 3/3] virtiofsd: check whether strdup lo.source return NULL in " Haotian Li 2020-11-11 1:10 ` [Virtio-fs] " Haotian Li 2020-11-11 19:55 ` Dr. David Alan Gilbert 2020-11-12 16:25 ` Dr. David Alan Gilbert [this message] 2020-11-12 16:25 ` [Virtio-fs] [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=20201112162550.GH13424@work-vm \ --to=dgilbert@redhat.com \ --cc=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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.