qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>
To: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] v9fs_walk: As per 9p2000 RFC, MAXWELEM >= nwnames >= 0.
Date: Mon, 21 Mar 2011 14:37:30 -0700	[thread overview]
Message-ID: <4D87C51A.6090204@linux.vnet.ibm.com> (raw)
In-Reply-To: <4D87C471.2000004@linux.vnet.ibm.com>

On 3/21/2011 2:34 PM, Venkateswararao Jujjuri (JV) wrote:
> On 3/21/2011 2:16 PM, Stefan Hajnoczi wrote:
>> On Mon, Mar 21, 2011 at 6:31 PM, Harsh Prateek Bora
>> <harsh@linux.vnet.ibm.com> wrote:
>>> The nwnames field in TWALK message is assumed to be >=0 and <= MAXWELEM
>>> which is defined as macro P9_MAXWELEM (16) in virtio-9p.h as per 9p2000 RFC.
>>> Appropriate changes are required in V9fsWalkState and v9fs_walk.
>>>
>>> Signed-off-by: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
>>> ---
>>>  hw/9pfs/virtio-9p.c |    5 ++++-
>>>  hw/9pfs/virtio-9p.h |    2 +-
>>>  2 files changed, 5 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/hw/9pfs/virtio-9p.c b/hw/9pfs/virtio-9p.c
>>> index 9b44bd0..b782a19 100644
>>> --- a/hw/9pfs/virtio-9p.c
>>> +++ b/hw/9pfs/virtio-9p.c
>>> @@ -1805,7 +1805,7 @@ static void v9fs_walk(V9fsState *s, V9fsPDU *pdu)
>>>     vs->offset += pdu_unmarshal(vs->pdu, vs->offset, "ddw", &fid,
>>>                                             &newfid, &vs->nwnames);
>>>
>>> -    if (vs->nwnames) {
>>> +    if (vs->nwnames <= P9_MAXWELEM) {
>>>         vs->wnames = qemu_mallocz(sizeof(vs->wnames[0]) * vs->nwnames);
>>>
>>>         vs->qids = qemu_mallocz(sizeof(vs->qids[0]) * vs->nwnames);
>>> @@ -1814,6 +1814,9 @@ static void v9fs_walk(V9fsState *s, V9fsPDU *pdu)
>>>             vs->offset += pdu_unmarshal(vs->pdu, vs->offset, "s",
>>>                                             &vs->wnames[i]);
>>>         }
>>> +    } else {
>>> +        err = -EINVAL;
> vs->nwnames  = 0; will take care of v9fs_walk_complete() issue Stefan brought up.
>>> +        goto out;

Or you can have same check "if (vs->nwnames <= P9_MAXWELEM) {" in the
v9fs_walk_complete() too; basically you need to be consistant with the checking.

- JV

>>>     }
>>
>> v9fs_walk_complete() will attempt to free wnames, qids, and the wnames
>> strings.  Freeing the strings will crash because we're indexing into
>> an array based off a NULL pointer.
>>
>> It would be very handy to have a PDU-level test suite.  You could then
>> construct a PDU with an invalid nwnames field and exercise this code
>> path.  Perhaps a debug ioctl in Linux v9fs that allows a userspace
>> tool to pass PDUs through will do?
> 
> Ioctl way was ruled out in the past discussion. But yes we have in plan on to
> introduce
> a test suite of this kind. Malahal (who is on vacation) will start this work
> from early April.
> 
> Thanks,
> JV
> 
>>
>> Stefan
> 

      reply	other threads:[~2011-03-21 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 18:31 [Qemu-devel] [PATCH] v9fs_walk: As per 9p2000 RFC, MAXWELEM >= nwnames >= 0 Harsh Prateek Bora
2011-03-21 21:16 ` Stefan Hajnoczi
2011-03-21 21:34   ` Venkateswararao Jujjuri (JV)
2011-03-21 21:37     ` Venkateswararao Jujjuri (JV) [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=4D87C51A.6090204@linux.vnet.ibm.com \
    --to=jvrao@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=harsh@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).