From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Harsh Bora <harsh@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] Ensure an error is reported to user if 9pfs mount tag is too long
Date: Thu, 29 Sep 2011 20:32:54 +0530 [thread overview]
Message-ID: <87mxdnqtlt.fsf@skywalker.in.ibm.com> (raw)
In-Reply-To: <1317292424-12239-1-git-send-email-berrange@redhat.com>
On Thu, 29 Sep 2011 11:33:44 +0100, "Daniel P. Berrange" <berrange@redhat.com> wrote:
> From: "Daniel P. Berrange" <berrange@redhat.com>
>
> If the 9pfs mount tag is longer than MAX_TAG_LEN bytes, rather than
> silently truncating the tag which will likely break the guest OS,
> report an immediate error and exit QEMU
>
> * hw/9pfs/virtio-9p-device.c: Report error & exit if mount tag is
> too long
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Applied to the VirtFS (git://repo.or.cz/qemu/v9fs.git). I have to apply
by hand, because it didn't apply cleanly. I also fixed checkpatch.pl errors.
> ---
> hw/9pfs/virtio-9p-device.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/hw/9pfs/virtio-9p-device.c b/hw/9pfs/virtio-9p-device.c
> index 97f2da5..8ca38d3 100644
> --- a/hw/9pfs/virtio-9p-device.c
> +++ b/hw/9pfs/virtio-9p-device.c
> @@ -117,7 +117,9 @@ VirtIODevice *virtio_9p_init(DeviceState *dev, V9fsConf *conf)
> s->ctx.fs_root = g_strdup(fse->path);
> len = strlen(conf->tag);
> if (len > MAX_TAG_LEN) {
> - len = MAX_TAG_LEN;
> + fprintf(stderr, "mount tag '%s' (%d bytes) is longer than maximum (%d bytes)",
> + conf->tag, len, MAX_TAG_LEN);
> + exit(1);
> }
> /* s->tag is non-NULL terminated string */
> s->tag = g_malloc(len);
> --
> 1.7.6.2
>
>
-aneesh
prev parent reply other threads:[~2011-09-29 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 10:33 [Qemu-devel] [PATCH] Ensure an error is reported to user if 9pfs mount tag is too long Daniel P. Berrange
2011-09-29 15:02 ` Aneesh Kumar K.V [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=87mxdnqtlt.fsf@skywalker.in.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=harsh@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).