From: Konrad@dumpdata.com, Rzeszutek@dumpdata.com, Wilk@dumpdata.com
To: stable@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Xen bug-fixes for 2.6.39 (already in 2.6.40)
Date: Wed, 25 May 2011 17:37:32 -0400 [thread overview]
Message-ID: <1306359456-3627-1-git-send-email-konrad.wilk@oracle.com> (raw)
Hey stable-tree maintainer(s).
The follow four patches are in the 2.6.40 tree and should be back-ported to 2.6.39 (only).
I forgot to CC:stable on them, so manually doing it here.
The four patches in question have the following git commits:
8c5950881c3b5e6e350e4b0438a8ccc513d90df9
xen/p2m: Create entries in the P2M_MFN trees's to track 1-1 mappings
0f16d0dfcdb5aab97d9e368f008b070b5b3ec6d3
xen/setup: Fix for incorrect xen_extra_mem_start initialization under 32-bit
15bfc094517db2ddf38ca7ed47f3a1c0ad24f7c4
xen/setup: Ignore E820_UNUSABLE when setting 1-1 mappings.
7899891c7d161752f29abcc9bc0a9c6c3a3af26c
xen mmu: fix a race window causing leave_mm BUG()
And are part of this email chain. Please apply them to 2.6.39.1 tree.
Thank you.
next reply other threads:[~2011-05-25 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 21:37 Konrad, Rzeszutek, Wilk [this message]
2011-05-25 21:37 ` [PATCH] xen mmu: fix a race window causing leave_mm BUG() Konrad, Rzeszutek, Wilk
2011-05-25 21:37 ` [PATCH] xen/p2m: Create entries in the P2M_MFN trees's to track 1-1 mappings Konrad, Rzeszutek, Wilk
2011-05-25 21:37 ` [PATCH 1/2] xen/setup: Ignore E820_UNUSABLE when setting " Konrad, Rzeszutek, Wilk
2011-05-25 21:37 ` [PATCH 2/2] xen/setup: Fix for incorrect xen_extra_mem_start initialization under 32-bit Konrad, Rzeszutek, Wilk
2011-05-26 7:02 ` [stable] [PATCH] Xen bug-fixes for 2.6.39 (already in 2.6.40) Greg KH
2011-05-26 12:39 ` Konrad Rzeszutek Wilk
2011-05-26 12:44 ` Tian, Kevin
2011-05-26 13:14 ` Daniel Kiper
2011-05-30 9:40 ` Greg KH
2011-05-31 14:26 ` Konrad Rzeszutek Wilk
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=1306359456-3627-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad@dumpdata.com \
--cc=Rzeszutek@dumpdata.com \
--cc=Wilk@dumpdata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.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
all inboxes | Powered by JetHome®