From: "M. Mohan Kumar" <mohan@in.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: jvrao@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] virtio-9p: Use clone approach to fix TOCTOU vulnerability
Date: Thu, 16 Jun 2011 16:58:44 +0530 [thread overview]
Message-ID: <20110616112844.GD3428@in.ibm.com> (raw)
In-Reply-To: <BANLkTi=o+5+AQ_6ieQNALAMj0heAuReSRA@mail.gmail.com>
On Wed, Jun 15, 2011 at 04:24:12PM +0100, Stefan Hajnoczi wrote:
> On Tue, Jun 14, 2011 at 9:12 AM, M. Mohan Kumar <mohan@in.ibm.com> wrote:
> > [RFC PATCH] virtio-9p: Use clone approach to fix TOCTOU vulnerability
> >
> > In passthrough security model, following a symbolic link in the server
> > side could result in TOCTTOU vulnerability.
> >
> > Use clone system call to create a thread which runs in chrooted
> > environment. All passthrough model file operations are done from this
> > thread to avoid TOCTTOU vulnerability.
> >
> > Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
> > Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
> > ---
> > fsdev/file-op-9p.h | 1 +
> > hw/9pfs/virtio-9p-coth.c | 105 +++++++++++++++++++++++++++++++++++++++++--
> > hw/9pfs/virtio-9p-coth.h | 13 +++++-
> > hw/9pfs/virtio-9p-device.c | 7 +++-
> > hw/9pfs/virtio-9p.h | 6 ++-
> > 5 files changed, 124 insertions(+), 8 deletions(-)
>
> This patch isn't against upstream virtio-9p. Please post a link to a
> repo or more information.
Hi Stefan,
Thanks for the detailed review. I will address review comments in next
version.
next prev parent reply other threads:[~2011-06-16 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 8:12 [Qemu-devel] [RFC PATCH] virtio-9p: Use clone approach to fix TOCTOU vulnerability M. Mohan Kumar
2011-06-15 15:24 ` Stefan Hajnoczi
2011-06-16 11:28 ` M. Mohan Kumar [this message]
2011-06-15 17:35 ` Stefan Hajnoczi
2011-06-15 18:16 ` Venkateswararao Jujjuri
2011-06-16 5:16 ` Stefan Hajnoczi
2011-06-15 20:10 ` Andreas Färber
2011-06-16 11:20 ` M. Mohan Kumar
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=20110616112844.GD3428@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=jvrao@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 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.