From: Juergen Gross <jgross@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
sstabellini@kernel.org
Subject: [GIT PULL] xen: branch for v6.8-rc5
Date: Thu, 15 Feb 2024 16:24:26 +0100 [thread overview]
Message-ID: <20240215152426.1114-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-6.8a-rc5-tag
xen: branch for v6.8-rc5
It contains the following fixes and simple cleanups:
- A fix using a proper flexible array instead of a one-element array in order to
avoid array-bounds sanitizer errors.
- A fix adding NULL pointer checks after allocating memory.
- A cleanup using memdup_array_user() instead of open-coding it.
- A fix for a rare race condition in Xen event channel allocation code.
- A small series making struct bus_type instances const.
- A fix of kerneldoc inline comments to match reality.
Thanks.
Juergen
arch/x86/xen/smp.c | 12 ++++++++++++
drivers/xen/events/events_base.c | 8 ++++++--
drivers/xen/gntalloc.c | 2 +-
drivers/xen/pcpu.c | 2 +-
drivers/xen/privcmd.c | 15 +++++----------
drivers/xen/xen-balloon.c | 2 +-
drivers/xen/xenbus/xenbus_client.c | 15 +++++++++------
include/uapi/xen/gntalloc.h | 5 ++++-
8 files changed, 39 insertions(+), 22 deletions(-)
Kees Cook (1):
xen/gntalloc: Replace UAPI 1-element array
Kunwu Chan (1):
x86/xen: Add some null pointer checking to smp.c
Markus Elfring (1):
xen/privcmd: Use memdup_array_user() in alloc_ioreq()
Maximilian Heyne (1):
xen/events: close evtchn after mapping cleanup
Ricardo B. Marliere (2):
xen: pcpu: make xen_pcpu_subsys const
xen: balloon: make balloon_subsys const
SeongJae Park (1):
xen/xenbus: document will_handle argument for xenbus_watch_path()
next reply other threads:[~2024-02-15 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 15:24 Juergen Gross [this message]
2024-02-15 19:50 ` 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=20240215152426.1114-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@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 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®