From: Juergen Gross <jgross@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
boris.ostrovsky@oracle.com
Subject: [GIT PULL] xen: branch for v5.11-rc1
Date: Tue, 15 Dec 2020 13:26:06 +0100 [thread overview]
Message-ID: <20201215122606.6874-1-jgross@suse.com> (raw)
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-5.11-rc1-tag
xen: branch for v5.11-rc1
It contains fixes for security issues just having been disclosed:
- a 5 patch series for fixing of XSA-349 (DoS via resource depletion in
Xen dom0)
- a patch fixing XSA-350 (access of stale pointer in a Xen dom0)
Thanks.
Juergen
drivers/block/xen-blkback/xenbus.c | 4 +++-
drivers/net/xen-netback/xenbus.c | 6 +++++-
drivers/xen/xen-pciback/xenbus.c | 2 +-
drivers/xen/xenbus/xenbus.h | 2 ++
drivers/xen/xenbus/xenbus_client.c | 8 +++++++-
drivers/xen/xenbus/xenbus_probe.c | 1 +
drivers/xen/xenbus/xenbus_probe_backend.c | 7 +++++++
drivers/xen/xenbus/xenbus_xs.c | 34 ++++++++++++++++++++-----------
include/xen/xenbus.h | 15 +++++++++++++-
9 files changed, 62 insertions(+), 17 deletions(-)
Pawel Wieczorkiewicz (1):
xen-blkback: set ring->xenblkd to NULL after kthread_stop()
SeongJae Park (5):
xen/xenbus: Allow watches discard events before queueing
xen/xenbus: Add 'will_handle' callback support in xenbus_watch_path()
xen/xenbus/xen_bus_type: Support will_handle watch callback
xen/xenbus: Count pending messages for each watch
xenbus/xenbus_backend: Disallow pending watch messages
next reply other threads:[~2020-12-15 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 12:26 Juergen Gross [this message]
2020-12-16 20:16 ` [GIT PULL] xen: branch for v5.11-rc1 pr-tracker-bot
2020-12-19 6:31 Juergen Gross
2020-12-19 21:06 ` pr-tracker-bot
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=20201215122606.6874-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xenproject.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.