From: Stefan Hajnoczi <stefanha@gmail.com>
To: "M. Mohan Kumar" <mohan@in.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-9p: Make rpath function thread safe
Date: Fri, 15 Apr 2011 10:42:21 +0100 [thread overview]
Message-ID: <BANLkTikdSULZgTT-RDECwR6n326wvD=aXw@mail.gmail.com> (raw)
In-Reply-To: <1302858357-11309-1-git-send-email-mohan@in.ibm.com>
On Fri, Apr 15, 2011 at 10:05 AM, M. Mohan Kumar <mohan@in.ibm.com> wrote:
> Use dynamically allocated memory to return concatenated path
> (fs_root and file path) instead of a static buffer. Caller has to free
> the memory.
>
> Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
> ---
> This patch depends on my chroot patchset.
> http://patchwork.ozlabs.org/patch/89033/
>
> hw/9pfs/virtio-9p-local.c | 551 ++++++++++++++++++++++++++-------------------
> hw/file-op-9p.h | 10 +-
> 2 files changed, 322 insertions(+), 239 deletions(-)
Would it be possible to build a const char *fs_ctx->path once in the
PDU handler for each operation that takes a path instead of pushing so
many rpath() calls down into virtio-9p-local.c? That way you don't
need to worry about constructing and freeing paths over and over.
I think it's time to kill errno once and for all in virtio-9p. The
errno global variable usage is getting out of hand; pretty much every
patch is adding boilerplate code to juggle around errno and avoid
trampling it. This new qemu_free() call means we need to juggle in
new places.
Please stop adding more errno juggling and just use -errno return
values. That change needs to happen before this patch.
> @@ -137,29 +164,10 @@ static int local_lstat(FsContext *fs_ctx, const char *path, struct stat *stbuf)
> }
> if (getxattr(rpath(fs_ctx, path), "user.virtfs.rdev", &tmp_dev,
> sizeof(dev_t)) > 0) {
Leak.
> tsize = readlink(rpath(fs_ctx, path), buf, bufsz);
Leak.
> -static void local_rewinddir(FsContext *ctx, DIR *dir)
> +static void local_rewinddir(FsContext *fs_ctx, DIR *dir)
> {
> return rewinddir(dir);
> }
Please do this in a separate patch.
> err = local_set_xattr(rpath(fs_ctx, newpath), credp);
Leak.
Stefan
next prev parent reply other threads:[~2011-04-15 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 9:05 [Qemu-devel] [PATCH] virtio-9p: Make rpath function thread safe M. Mohan Kumar
2011-04-15 9:42 ` Stefan Hajnoczi [this message]
2011-04-15 15:02 ` Venkateswararao Jujjuri
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='BANLkTikdSULZgTT-RDECwR6n326wvD=aXw@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=mohan@in.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).