From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: xen-devel@lists.xen.org
Subject: [GIT PULL] (xen) stable/for-linus-3.8-rc6-tag
Date: Wed, 6 Feb 2013 12:16:15 -0500 [thread overview]
Message-ID: <20130206171615.GG24458@konrad-lan.dumpdata.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 780 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.8-rc6-tag
Which has two fixes. One is a security fix wherein we would spam the kernel
printk buffer if one of the guests was misbehaving. The other is much tamer
and it was us only checking for one type of error from the IRQ subsystem (when
allocating new IRQs) instead of for all of them.
Please pull!
drivers/xen/events.c | 4 ++--
drivers/xen/xen-pciback/pciback_ops.c | 14 +++++++-------
2 files changed, 9 insertions(+), 9 deletions(-)
Jan Beulich (1):
xen-pciback: rate limit error messages from xen_pcibk_enable_msi{,x}()
Wei Liu (1):
xen: fix error handling path if xen_allocate_irq_dynamic fails
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
reply other threads:[~2013-02-06 17:16 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=20130206171615.GG24458@konrad-lan.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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
Powered by JetHome