From: Andrea Arcangeli <aarcange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: 2.6.38.1 general protection fault
Date: Mon, 28 Mar 2011 19:54:37 +0200 [thread overview]
Message-ID: <20110328175437.GB12265@random.random> (raw)
In-Reply-To: <4D9052B7.2070508@redhat.com>
Hello everyone,
On Mon, Mar 28, 2011 at 11:19:51AM +0200, Avi Kivity wrote:
> On 03/28/2011 08:24 AM, Tomasz Chmielewski wrote:
> > On 27.03.2011 11:42, Avi Kivity wrote:
> >
> > (...)
> >
> >> Okay, the fork came from the ,script=.
> >>
> >> The issue with %rsi looks like a use-after-free, however
> >> kvm_mmu_notifier_invalidate_range_start appears to be properly srcu
> >> protected.
> >
> > FYI, I saw this one as well:
> >
> > http://www.virtall.com/files/temp/kvm.txt
>
> Similar pattern - top 16 bits of %rsi are flipped.
>
> Marcelo, what was the option to enable padding for allocations and
> overrun detection? Also use-after-free?
BTW, is it genuine that a protection fault is generated instead of a page
fault while dereferencing address 0x00008805d6b087f8? I would normally
except a page fault from a memory dereference that doesn't alter
processor state/segments.
The other GFP happened in pmdp_clear_flush_notify inside
collapse_huge_page.
next prev parent reply other threads:[~2011-03-28 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 9:32 2.6.38.1 general protection fault Tomasz Chmielewski
2011-03-26 9:15 ` Avi Kivity
2011-03-26 10:42 ` Tomasz Chmielewski
2011-03-27 9:42 ` Avi Kivity
2011-03-28 6:24 ` Tomasz Chmielewski
2011-03-28 9:19 ` Avi Kivity
2011-03-28 17:54 ` Andrea Arcangeli [this message]
2011-03-28 18:02 ` Avi Kivity
2011-03-28 20:04 ` Andrea Arcangeli
2011-03-28 20:14 ` Tomasz Chmielewski
2011-04-20 9:28 ` Thomas Treutner
2011-04-20 10:54 ` Tomasz Chmielewski
2011-03-29 13:34 ` Marcelo Tosatti
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=20110328175437.GB12265@random.random \
--to=aarcange@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox