From: Ian Campbell <ian.campbell@citrix.com>
To: Corneliu ZUZU <czuzu@bitdefender.com>, xen-devel@lists.xen.org
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: [PATCH V2] arm: p2m.c bug-fix: hypervisor hang on __p2m_get_mem_access
Date: Wed, 3 Feb 2016 12:23:53 +0000 [thread overview]
Message-ID: <1454502233.25207.107.camel@citrix.com> (raw)
In-Reply-To: <56B1EA8E.3070100@bitdefender.com>
On Wed, 2016-02-03 at 13:54 +0200, Corneliu ZUZU wrote:
> On 2/3/2016 1:48 PM, Ian Campbell wrote:
> > On Wed, 2016-01-27 at 14:24 +0200, Corneliu ZUZU wrote:
> > > When __p2m_get_mem_access gets called, the p2m lock is already taken
> > > by either get_page_from_gva or p2m_get_mem_access.
> > >
> > > Possible code paths:
> > > 1) -> get_page_from_gva
> > > -> p2m_mem_access_check_and_get_page
> > > -> __p2m_get_mem_access
> > > 2) -> p2m_get_mem_access
> > > -> __p2m_get_mem_access
> > >
> > > In both cases if __p2m_get_mem_access subsequently gets to
> > > call p2m_lookup (happens if !radix_tree_lookup(...)), a hypervisor
> > > hang will occur, since p2m_lookup also spin-locks on the p2m lock.
> > >
> > > This bug-fix simply replaces the p2m_lookup call from
> > > __p2m_get_mem_access
> > > with a call to __p2m_lookup.
> > >
> > > Following Ian's suggestion, we also add an ASSERT to ensure that
> > > the p2m lock is taken upon __p2m_get_mem_access entry.
> > >
> > > Signed-off-by: Corneliu ZUZU <czuzu@bitdefender.com>
> > Acked + applied, thanks.
> >
> >
> I thought this mail was not sent properly (didn't find it any longer on
> the web (?)) and I resent it just earlier.
> I figured it must've been the fact that I forgot to put a "Changed since
> v1" section & that I didn't include an
> "--in-reply-to" option. Apparently it was actually sent correctly.
> Sorry, ignore the last one (which contains a "Changed since v1" section).
OK, please check that what is currently in xen.git#staging is what you
think should be there.
Ian.
next prev parent reply other threads:[~2016-02-03 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 12:24 [PATCH V2] arm: p2m.c bug-fix: hypervisor hang on __p2m_get_mem_access Corneliu ZUZU
2016-02-03 11:48 ` Ian Campbell
2016-02-03 11:54 ` Corneliu ZUZU
2016-02-03 12:23 ` Ian Campbell [this message]
2016-02-03 12:28 ` Corneliu ZUZU
-- strict thread matches above, loose matches on Subject: below --
2016-01-26 11:46 [PATCH] " Corneliu ZUZU
2016-02-03 11:37 ` [PATCH v2] " Corneliu ZUZU
2016-02-03 11:52 ` Ian Campbell
2016-02-03 11:56 ` Corneliu ZUZU
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=1454502233.25207.107.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=czuzu@bitdefender.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.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.