From: Harsh Bora <harsh@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "M. Mohan Kumar" <mohan@in.ibm.com>,
jvrao@linux.vnet.ibm.com, qemu-devel@nongnu.org,
"Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: [Qemu-devel] Re: [PATCH v3] v9fs_walk: As per 9p2000 RFC, MAXWELEM >= nwnames >= 0.
Date: Tue, 05 Apr 2011 16:00:08 +0530 [thread overview]
Message-ID: <4D9AEF30.5070206@linux.vnet.ibm.com> (raw)
In-Reply-To: <BANLkTikkf5JEPAUjboQBxfg1jj0O3mHZuQ@mail.gmail.com>
On 04/05/2011 02:24 PM, Stefan Hajnoczi wrote:
> On Tue, Apr 5, 2011 at 6:56 AM, 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.
>>
>> v3:
>> - Updated if-else conditions to appropriately handle nwnames = 0.
>>
>> v2:
>> - Added check in v9fs_walk_complete as well.
>>
>> Signed-off-by: Harsh Prateek Bora<harsh@linux.vnet.ibm.com>
>> ---
>> hw/9pfs/virtio-9p.c | 7 +++++--
>> hw/9pfs/virtio-9p.h | 2 +-
>> 2 files changed, 6 insertions(+), 3 deletions(-)
>
> hw/virtio-9p.c
>
> I think you've submitted a patch against an internal tree that isn't upstream.
Yes, it is based on a patch yet to be merged in mainline by Aneesh which
will move 9p files into a separate folder, however, I shall repost an
updated version of the patch based on current directory structure.
regards,
Harsh
>
> Stefan
prev parent reply other threads:[~2011-04-05 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 5:56 [Qemu-devel] [PATCH v3] v9fs_walk: As per 9p2000 RFC, MAXWELEM >= nwnames >= 0 Harsh Prateek Bora
2011-04-05 8:54 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-05 10:30 ` Harsh Bora [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=4D9AEF30.5070206@linux.vnet.ibm.com \
--to=harsh@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=mohan@in.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).