From: Rafael Aquini <aquini@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] virtio_balloon: leak_balloon(): only tell host if we got pages deflated
Date: Wed, 5 Jun 2013 20:29:33 -0300 [thread overview]
Message-ID: <20130605232932.GA30387@optiplex.redhat.com> (raw)
In-Reply-To: <20130605190844.1e96bbde@redhat.com>
On Wed, Jun 05, 2013 at 07:08:44PM -0400, Luiz Capitulino wrote:
> On Wed, 5 Jun 2013 18:24:49 -0300
> Rafael Aquini <aquini@redhat.com> wrote:
>
> > On Wed, Jun 05, 2013 at 05:10:31PM -0400, Luiz Capitulino wrote:
> > > The balloon_page_dequeue() function can return NULL. If it does for
> > > the first page being freed, then leak_balloon() will create a
> > > scatter list with len=0. Which in turn seems to generate an invalid
> > > virtio request.
> > >
> > > Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> > > ---
> > >
> > > PS: I didn't get this in practice. I found it by code review. On the other
> > > hand, automatic-ballooning was able to put such invalid requests in
> > > the virtqueue and QEMU would explode...
> > >
> >
> > Nice catch! The patch looks sane and replicates the check done at
> > fill_balloon(). I think we also could use this P.S. as a commentary
> > to let others aware of this scenario. Thanks Luiz!
>
> Want me to respin?
>
That would be great, indeed. I guess the commentary could also go for the same
if case at fill_balloon(), assuming the tests are placed to prevent the same
scenario you described at changelog. You can stick my Ack on it, if reposting.
Cheers!
-- Rafael
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Rafael Aquini <aquini@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] virtio_balloon: leak_balloon(): only tell host if we got pages deflated
Date: Wed, 5 Jun 2013 20:29:33 -0300 [thread overview]
Message-ID: <20130605232932.GA30387@optiplex.redhat.com> (raw)
In-Reply-To: <20130605190844.1e96bbde@redhat.com>
On Wed, Jun 05, 2013 at 07:08:44PM -0400, Luiz Capitulino wrote:
> On Wed, 5 Jun 2013 18:24:49 -0300
> Rafael Aquini <aquini@redhat.com> wrote:
>
> > On Wed, Jun 05, 2013 at 05:10:31PM -0400, Luiz Capitulino wrote:
> > > The balloon_page_dequeue() function can return NULL. If it does for
> > > the first page being freed, then leak_balloon() will create a
> > > scatter list with len=0. Which in turn seems to generate an invalid
> > > virtio request.
> > >
> > > Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> > > ---
> > >
> > > PS: I didn't get this in practice. I found it by code review. On the other
> > > hand, automatic-ballooning was able to put such invalid requests in
> > > the virtqueue and QEMU would explode...
> > >
> >
> > Nice catch! The patch looks sane and replicates the check done at
> > fill_balloon(). I think we also could use this P.S. as a commentary
> > to let others aware of this scenario. Thanks Luiz!
>
> Want me to respin?
>
That would be great, indeed. I guess the commentary could also go for the same
if case at fill_balloon(), assuming the tests are placed to prevent the same
scenario you described at changelog. You can stick my Ack on it, if reposting.
Cheers!
-- Rafael
next prev parent reply other threads:[~2013-06-05 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 21:10 [PATCH] virtio_balloon: leak_balloon(): only tell host if we got pages deflated Luiz Capitulino
2013-06-05 21:10 ` Luiz Capitulino
2013-06-05 21:24 ` Rafael Aquini
2013-06-05 21:24 ` Rafael Aquini
2013-06-05 23:08 ` Luiz Capitulino
2013-06-05 23:08 ` Luiz Capitulino
2013-06-05 23:29 ` Rafael Aquini [this message]
2013-06-05 23:29 ` Rafael Aquini
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=20130605232932.GA30387@optiplex.redhat.com \
--to=aquini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.