All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Oscon <oscon@mail.datanet.hu>
Cc: kvm@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: kernel memory allocation bug in 2.6.27.32-2.6.27.41 kvm section
Date: Sun, 27 Dec 2009 12:13:00 +0200	[thread overview]
Message-ID: <4B37332C.4020100@redhat.com> (raw)
In-Reply-To: <200912171635.07009.oscon@mail.datanet.hu>

On 12/17/2009 05:35 PM, Oscon wrote:
> Hello!
>
> I can't register new account in bugzilla.kernel.org. / my ISP's spamfilter
> problem (?) maybe./
>
> --------------------------
>
> I sent this mail to Greg KH (2.6.27.y maintainer), he sent me:
>
> "Can you get the kvm maintainers to agree that this is correct?
>
> thanks,
>
> greg k-h"
>
> ---------------
> So the bug :
>
> I found a memory allocation bug in kvm/mmu.c&  kvm_main.c. /in
> kvm_destroy_vm()/
>
> Affected kernel: 2.6.27.32-2.6.27.41
>
> Mainline kernel (2.6.32) is not affected. (Modified kvm subsystem.)
>
> Cause:
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fstable%2Flinux-2.6.27.y.git;a=commitdiff_plain;h=d2127c8300fb1ec54af56faee17170e7a525326d
>
> Solution: Revert this patch.
>
> This bug can cause local DoS in the host system.
>
>    


Looks like some other patch is missing in 2.6.27.y.  Not sure what it is.

But it's safer to revert this patch for now.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-12-27 10:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 15:35 kernel memory allocation bug in 2.6.27.32-2.6.27.41 kvm section Oscon
2009-12-27 10:13 ` Avi Kivity [this message]
2010-01-05 19:37   ` Greg KH

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=4B37332C.4020100@redhat.com \
    --to=avi@redhat.com \
    --cc=greg@kroah.com \
    --cc=kvm@vger.kernel.org \
    --cc=oscon@mail.datanet.hu \
    /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.