From: Julien Grall <julien.grall@arm.com>
To: xen-devel@lists.xen.org
Cc: Julien Grall <julien.grall@arm.com>,
sstabellini@kernel.org, wei.liu2@citrix.com, wei.chen@arm.com
Subject: [for-4.7 2/2] xen/arm: p2m: Release the p2m lock before undoing the mappings
Date: Mon, 16 May 2016 15:08:55 +0100 [thread overview]
Message-ID: <1463407735-7409-3-git-send-email-julien.grall@arm.com> (raw)
In-Reply-To: <1463407735-7409-1-git-send-email-julien.grall@arm.com>
Since commit 4b25423a "arch/arm: unmap partially-mapped memory regions",
Xen has been undoing the P2M mappings when an error occurred during
insertion or memory allocation.
This is done by calling recursively apply_p2m_changes, however the
second call is done with the p2m lock taken which will result in a
deadlock for the current processor.
Fix it by moving the recursive call after the lock has been released.
Signed-off-by: Julien Grall <julien.grall@arm.com>
---
I think we could unlock the p2m lock before freeing the temporary
mapping. Although, I played safe as this is a bug fix for Xen 4.7
and to be backported up to Xen 4.5.
---
xen/arch/arm/p2m.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/xen/arch/arm/p2m.c b/xen/arch/arm/p2m.c
index 68c67b0..838d004 100644
--- a/xen/arch/arm/p2m.c
+++ b/xen/arch/arm/p2m.c
@@ -1184,6 +1184,14 @@ out:
while ( (pg = page_list_remove_head(&free_pages)) )
free_domheap_page(pg);
+ for ( level = P2M_ROOT_LEVEL; level < 4; level ++ )
+ {
+ if ( mappings[level] )
+ unmap_domain_page(mappings[level]);
+ }
+
+ spin_unlock(&p2m->lock);
+
if ( rc < 0 && ( op == INSERT || op == ALLOCATE ) &&
addr != start_gpaddr )
{
@@ -1196,14 +1204,6 @@ out:
mattr, 0, p2m_invalid, d->arch.p2m.default_access);
}
- for ( level = P2M_ROOT_LEVEL; level < 4; level ++ )
- {
- if ( mappings[level] )
- unmap_domain_page(mappings[level]);
- }
-
- spin_unlock(&p2m->lock);
-
return rc;
}
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-16 14:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 14:08 [for-4.7 0/2] xen/arm: Bug fixes in the P2M code Julien Grall
2016-05-16 14:08 ` [for-4.7 1/2] xen/arm: p2m: apply_p2m_changes: Do not undo more than necessary Julien Grall
2016-05-17 6:40 ` Wei Chen
2016-05-17 7:29 ` Julien Grall
2016-05-17 11:18 ` Stefano Stabellini
2016-05-16 14:08 ` Julien Grall [this message]
2016-05-17 5:45 ` [for-4.7 2/2] xen/arm: p2m: Release the p2m lock before undoing the mappings Wei Chen
2016-05-17 6:21 ` Wei Chen
2016-05-17 11:24 ` Stefano Stabellini
2016-05-17 11:35 ` Julien Grall
2016-05-17 12:27 ` Stefano Stabellini
2016-05-17 12:48 ` Julien Grall
2016-05-18 10:10 ` Stefano Stabellini
2016-05-18 10:31 ` Julien Grall
2016-05-18 10:45 ` Julien Grall
2016-05-18 10:39 ` [for-4.7 0/2] xen/arm: Bug fixes in the P2M code Stefano Stabellini
2016-05-18 10:46 ` Wei Liu
2016-05-18 10:58 ` Julien Grall
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=1463407735-7409-3-git-send-email-julien.grall@arm.com \
--to=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=wei.chen@arm.com \
--cc=wei.liu2@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 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).