From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Linux 5.19.3
Date: Sun, 21 Aug 2022 15:35:44 +0200 [thread overview]
Message-ID: <1661088945124200@kroah.com> (raw)
I'm announcing the release of the 5.19.3 kernel.
All users of the 5.19 kernel series must upgrade.
The updated 5.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.19.y
and can be browsed at the normal kernel.org git web browser:
https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
thanks,
greg k-h
------------
Makefile | 2 -
arch/arm64/kernel/kexec_image.c | 11 ------
arch/x86/kernel/kexec-bzimage64.c | 20 -----------
drivers/tee/tee_shm.c | 3 +
fs/btrfs/raid56.c | 68 ++++++++++++++++++++++++++++++--------
include/linux/kexec.h | 7 +++
kernel/kexec_file.c | 17 +++++++++
mm/kfence/core.c | 18 +++++-----
net/sched/cls_route.c | 10 +++++
9 files changed, 104 insertions(+), 52 deletions(-)
Coiby Xu (2):
kexec, KEYS: make the code in bzImage64_verify_sig generic
arm64: kexec_file: use more system keyrings to verify kernel image signature
Greg Kroah-Hartman (1):
Linux 5.19.3
Jamal Hadi Salim (1):
net_sched: cls_route: disallow handle of 0
Jens Wiklander (1):
tee: add overflow check in register_shm_helper()
Marco Elver (1):
Revert "mm: kfence: apply kmemleak_ignore_phys on early allocated pool"
Qu Wenruo (2):
btrfs: only write the sectors in the vertical stripe which has data stripes
btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()
next reply other threads:[~2022-08-21 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 13:35 Greg Kroah-Hartman [this message]
2022-08-21 13:35 ` Linux 5.19.3 Greg Kroah-Hartman
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=1661088945124200@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@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 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.