From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, slade@sladewatkins.com
Subject: [PATCH 5.15 00/10] 5.15.62-rc2 review
Date: Sat, 20 Aug 2022 20:23:24 +0200 [thread overview]
Message-ID: <20220820182309.607584465@linuxfoundation.org> (raw)
This is the start of the stable review cycle for the 5.15.62 release.
There are 10 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Mon, 22 Aug 2022 18:23:01 +0000.
Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.62-rc2.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 5.15.62-rc2
Qu Wenruo <wqu@suse.com>
btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()
Qu Wenruo <wqu@suse.com>
btrfs: only write the sectors in the vertical stripe which has data stripes
Peter Zijlstra <peterz@infradead.org>
x86/ftrace: Use alternative RET encoding
Peter Zijlstra <peterz@infradead.org>
x86/ibt,ftrace: Make function-graph play nice
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Revert "x86/ftrace: Use alternative RET encoding"
Namjae Jeon <linkinjeon@kernel.org>
ksmbd: fix heap-based overflow in set_ntacl_dacl()
Hyunchul Lee <hyc.lee@gmail.com>
ksmbd: prevent out of bound read for SMB2_WRITE
Jamal Hadi Salim <jhs@mojatatu.com>
net_sched: cls_route: disallow handle of 0
Jens Wiklander <jens.wiklander@linaro.org>
tee: add overflow check in register_shm_helper()
Jens Axboe <axboe@kernel.dk>
io_uring: use original request task for inflight tracking
-------------
Diffstat:
Makefile | 4 +-
arch/x86/kernel/ftrace.c | 7 +--
arch/x86/kernel/ftrace_64.S | 19 +++++--
drivers/tee/tee_shm.c | 3 +
fs/btrfs/raid56.c | 74 +++++++++++++++++++------
fs/io_uring.c | 2 +-
fs/ksmbd/smb2misc.c | 7 ++-
fs/ksmbd/smb2pdu.c | 45 +++++++++------
fs/ksmbd/smbacl.c | 130 ++++++++++++++++++++++++++++++--------------
fs/ksmbd/smbacl.h | 2 +-
fs/ksmbd/vfs.c | 5 ++
net/sched/cls_route.c | 10 ++++
12 files changed, 216 insertions(+), 92 deletions(-)
next reply other threads:[~2022-08-21 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 18:23 Greg Kroah-Hartman [this message]
2022-08-21 12:09 ` [PATCH 5.15 00/10] 5.15.62-rc2 review Guenter Roeck
2022-08-21 15:32 ` Stafford Horne
2022-08-21 22:47 ` Guenter Roeck
2022-08-22 10:31 ` Naresh Kamboju
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=20220820182309.607584465@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).