From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] (xen) stable/for-linus-3.7-rc4-tag
Date: Fri, 2 Nov 2012 11:44:07 -0400 [thread overview]
Message-ID: <20121102154332.GA3923@konrad-lan.dumpdata.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
Hey Linus,
Please git pull the following tag:
git pull git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.7-rc4-tag
which has the following fixes (copy-n-paste from the signed tag):
<tag>
Bug-fixes:
* Use appropriate macros instead of hand-rolling our own (ARM).
* Fixes if FB/KBD closed unexpectedly.
* Fix memory leak in /dev/gntdev ioctl calls.
* Fix overflow check in xenbus_file_write.
* Document cleanup.
* Performance optimization when migrating guests.
</tag>
Nothing major - rather just incremental fixes.
arch/arm/xen/hypercall.S | 14 +++++--------
arch/x86/include/asm/xen/hypervisor.h | 1 -
arch/x86/xen/mmu.c | 21 ++++++++++++++++++-
drivers/input/misc/xen-kbdfront.c | 5 ++++-
drivers/video/xen-fbfront.c | 5 ++++-
drivers/xen/gntdev.c | 36 +++++++++++++++++---------------
drivers/xen/xenbus/xenbus_dev_frontend.c | 2 +-
include/trace/events/xen.h | 8 +++++++
8 files changed, 61 insertions(+), 31 deletions(-)
David Vrabel (3):
xen/gntdev: don't leak memory from IOCTL_GNTDEV_MAP_GRANT_REF
xen-fbfront: handle backend CLOSED without CLOSING
xen-kbdfront: handle backend CLOSED without CLOSING
Jan Beulich (1):
xen/xenbus: fix overflow check in xenbus_file_write()
Konrad Rzeszutek Wilk (1):
xen/mmu: Use Xen specific TLB flush instead of the generic one.
Olaf Hering (1):
x86: remove obsolete comment from asm/xen/hypervisor.h
Stefano Stabellini (1):
xen/arm: use the __HVC macro
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
reply other threads:[~2012-11-02 15:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121102154332.GA3923@konrad-lan.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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