From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
kvm@vger.kernel.org, virtualization@lists.osdl.org
Subject: Re: [PATCH] vhost: access check thinko fixes
Date: Mon, 4 Jan 2010 12:52:56 +1030 [thread overview]
Message-ID: <201001041252.57997.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20091224060058.GA26101@redhat.com>
On Thu, 24 Dec 2009 04:30:58 pm Michael S. Tsirkin wrote:
> This fixes two issues with recent access checking patch:
> 1. if (&d->vqs[i].private_data) -> if (d->vqs[i].private_data)
> 2. we can't forbid log base changes while ring is running,
> because host needs to resize log in rare cases
> (e.g. when memory is added with a baloon)
> and in that case it needs to increase log size with realloc,
> which might move the log address.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Thanks, applied.
Rusty.
prev parent reply other threads:[~2010-01-04 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 6:00 [PATCH] vhost: access check thinko fixes Michael S. Tsirkin
2010-01-04 2:22 ` Rusty Russell [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=201001041252.57997.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=virtualization@lists.osdl.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).