From: "Michael S. Tsirkin" <mst@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: kwolf@redhat.com, stefanha@redhat.com, luonengjun@huawei.com,
qemu-devel@nongnu.org, lcapitulino@redhat.com, alex@alex.org.uk,
pbonzini@redhat.com, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH 4/4] ivshmem: check the value returned by fstat()
Date: Tue, 5 Aug 2014 12:00:24 +0200 [thread overview]
Message-ID: <20140805100024.GC24619@redhat.com> (raw)
In-Reply-To: <53E03AC9.2070806@huawei.com>
On Tue, Aug 05, 2014 at 10:00:41AM +0800, zhanghailiang wrote:
> Hi Michael,
> Thanks for your review of this patch!
>
> >On Mon, Aug 04, 2014 at 04:25:44PM +0800, zhanghailiang wrote:
> >>The function fstat() may fail, so check its return value.
> >>
> >>Signed-off-by: zhanghailiang<zhang.zhanghailiang@huawei.com>
> >>---
> >> hw/misc/ivshmem.c | 5 ++++-
> >> 1 file changed, 4 insertions(+), 1 deletion(-)
> >>
> >>diff --git a/hw/misc/ivshmem.c b/hw/misc/ivshmem.c
> >>index 768e528..2667e9f 100644
> >>--- a/hw/misc/ivshmem.c
> >>+++ b/hw/misc/ivshmem.c
> >>@@ -324,7 +324,10 @@ static int check_shm_size(IVShmemState *s, int fd) {
> >>
> >> struct stat buf;
> >>
> >>- fstat(fd,&buf);
> >>+ if (fstat(fd,&buf)< 0) {
> >>+ fprintf(stderr, "Cannot stat IVSHMEM: %s\n", strerror(errno));
> >>+ return -1;
> >>+ }
> >>
> >
> >That's a confusing error message:
> >1. You don't stat ivshmem. You stat a shmem fd. Also best to print fd #.
> I will add this in next version of the patch.
> >2. Tell the user what action was taken, e.g. IVSHMEM failed to start.
> >
> >> if (s->ivshmem_size> buf.st_size) {
> >> fprintf(stderr,
> >>--
> I have check the places of calling this function, And found that, if this
> function return -1, qemu will call exit(-1). One of the callers is
> ivshmem_read(), the purpose of check_shm_size() is to forbid guest to map
> more memory than the object has allocated. So here is it suitable to return
> -1 if fstat() failed? Or just give a warning message and return 0?
> what's your opinion? Thanks.
So put "exiting" In the error message then.
> >>1.7.12.4
> >>
> >
> >.
> >
>
> Best regards,
> zhanghailiang
prev parent reply other threads:[~2014-08-05 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 8:25 [Qemu-devel] [PATCH 0/4] fix several bugs about use-after-free and an api abuse zhanghailiang
2014-08-04 8:25 ` [Qemu-devel] [PATCH 1/4] l2cap: fix access freed memory zhanghailiang
2014-08-04 8:37 ` Alex Bennée
2014-08-04 8:25 ` [Qemu-devel] [PATCH 2/4] monitor: " zhanghailiang
2014-08-04 9:01 ` Alex Bennée
2014-08-05 2:37 ` zhanghailiang
2014-08-04 8:25 ` [Qemu-devel] [PATCH 3/4] virtio-blk: fix reference a pointer which might be freed zhanghailiang
2014-08-04 11:14 ` Stefan Hajnoczi
2014-08-04 8:25 ` [Qemu-devel] [PATCH 4/4] ivshmem: check the value returned by fstat() zhanghailiang
2014-08-04 12:26 ` Michael S. Tsirkin
2014-08-05 2:00 ` zhanghailiang
2014-08-05 6:50 ` Levente Kurusa
2014-08-05 7:08 ` zhanghailiang
2014-08-05 10:00 ` Michael S. Tsirkin [this message]
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=20140805100024.GC24619@redhat.com \
--to=mst@redhat.com \
--cc=alex@alex.org.uk \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=luonengjun@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=zhang.zhanghailiang@huawei.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 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.