This is the start of the stable review cycle for the 5.19.3 release.
There are 7 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 Sun, 21 Aug 2022 15:36:59 +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.19.3-rc1…
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.19.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
Linux 5.19.3-rc1
Coiby Xu <coxu(a)redhat.com>
arm64: kexec_file: use more system keyrings to verify kernel image signature
Coiby Xu <coxu(a)redhat.com>
kexec, KEYS: make the code in bzImage64_verify_sig generic
Qu Wenruo <wqu(a)suse.com>
btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()
Qu Wenruo <wqu(a)suse.com>
btrfs: only write the sectors in the vertical stripe which has data stripes
Jamal Hadi Salim <jhs(a)mojatatu.com>
net_sched: cls_route: disallow handle of 0
Jens Wiklander <jens.wiklander(a)linaro.org>
tee: add overflow check in register_shm_helper()
Marco Elver <elver(a)google.com>
Revert "mm: kfence: apply kmemleak_ignore_phys on early allocated pool"
-------------
Diffstat:
Makefile | 4 +--
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, 105 insertions(+), 53 deletions(-)
This is the start of the stable review cycle for the 5.15.62 release.
There are 14 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 Sun, 21 Aug 2022 15:36:59 +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-rc…
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(a)linuxfoundation.org>
Linux 5.15.62-rc1
Coiby Xu <coxu(a)redhat.com>
arm64: kexec_file: use more system keyrings to verify kernel image signature
Coiby Xu <coxu(a)redhat.com>
kexec, KEYS: make the code in bzImage64_verify_sig generic
Coiby Xu <coxu(a)redhat.com>
kexec: clean up arch_kexec_kernel_verify_sig
Naveen N. Rao <naveen.n.rao(a)linux.vnet.ibm.com>
kexec_file: drop weak attribute from functions
Qu Wenruo <wqu(a)suse.com>
btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()
Qu Wenruo <wqu(a)suse.com>
btrfs: only write the sectors in the vertical stripe which has data stripes
Peter Zijlstra <peterz(a)infradead.org>
x86/ftrace: Use alternative RET encoding
Peter Zijlstra <peterz(a)infradead.org>
x86/ibt,ftrace: Make function-graph play nice
Thadeu Lima de Souza Cascardo <cascardo(a)canonical.com>
Revert "x86/ftrace: Use alternative RET encoding"
Namjae Jeon <linkinjeon(a)kernel.org>
ksmbd: fix heap-based overflow in set_ntacl_dacl()
Hyunchul Lee <hyc.lee(a)gmail.com>
ksmbd: prevent out of bound read for SMB2_WRITE
Jamal Hadi Salim <jhs(a)mojatatu.com>
net_sched: cls_route: disallow handle of 0
Jens Wiklander <jens.wiklander(a)linaro.org>
tee: add overflow check in register_shm_helper()
Jens Axboe <axboe(a)kernel.dk>
io_uring: use original request task for inflight tracking
-------------
Diffstat:
Makefile | 4 +-
arch/arm64/include/asm/kexec.h | 4 +-
arch/arm64/kernel/kexec_image.c | 11 +---
arch/powerpc/include/asm/kexec.h | 9 +++
arch/s390/include/asm/kexec.h | 3 +
arch/x86/include/asm/kexec.h | 6 ++
arch/x86/kernel/ftrace.c | 7 +-
arch/x86/kernel/ftrace_64.S | 19 ++++--
arch/x86/kernel/kexec-bzimage64.c | 20 +-----
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 ++
include/linux/kexec.h | 50 ++++++++++++---
kernel/kexec_file.c | 83 +++++++++---------------
net/sched/cls_route.c | 10 +++
20 files changed, 312 insertions(+), 182 deletions(-)
-------------------
NOTE, this is the LAST 5.18.y stable release. This tree will be
end-of-life after this one. Please move to 5.19.y at this point in time
or let us know why that is not possible.
-------------------
This is the start of the stable review cycle for the 5.18.19 release.
There are 6 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 Sun, 21 Aug 2022 15:36:59 +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.18.19-rc…
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.18.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
Linux 5.18.19-rc1
Coiby Xu <coxu(a)redhat.com>
arm64: kexec_file: use more system keyrings to verify kernel image signature
Coiby Xu <coxu(a)redhat.com>
kexec, KEYS: make the code in bzImage64_verify_sig generic
Qu Wenruo <wqu(a)suse.com>
btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()
Qu Wenruo <wqu(a)suse.com>
btrfs: only write the sectors in the vertical stripe which has data stripes
Jamal Hadi Salim <jhs(a)mojatatu.com>
net_sched: cls_route: disallow handle of 0
Jens Wiklander <jens.wiklander(a)linaro.org>
tee: add overflow check in register_shm_helper()
-------------
Diffstat:
Makefile | 4 +--
arch/arm64/kernel/kexec_image.c | 11 +-----
arch/x86/kernel/kexec-bzimage64.c | 20 +----------
drivers/tee/tee_shm.c | 3 ++
fs/btrfs/raid56.c | 74 ++++++++++++++++++++++++++++++---------
include/linux/kexec.h | 7 ++++
kernel/kexec_file.c | 17 +++++++++
net/sched/cls_route.c | 10 ++++++
8 files changed, 98 insertions(+), 48 deletions(-)
On Tue, Aug 16, 2022 at 01:56:14PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > This is the start of the stable review cycle for the 5.19.2 release.
> > > > There are 1157 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.
> > >
> > > Hi Greg,
> > >
> > > Perhaps its time that you just send a single email to LKML pointing where to
> > > find the stable releases. These patch bombs are bringing vger down to its
> > > knees, and causing delays in people's workflows. This doesn't just affect
> > > LKML, but all other vger mailing lists. Probably because LKML has the biggest
> > > subscriber base that patch bombs to it can slow everything else down.
> > >
> > > I sent 3 patches to the linux-trace-devel list almost 4 hours ago, and they
> > > still haven't shown up. I was going to point people to it tonight but it's now
> > > going to have to wait till tomorrow.
> >
> > Email is async, sometimes it takes longer than others to recieve
> > messages.
>
> Well, email is pretty fast most of the month.
>
> > My "patch bombs" get sent out slow to the mail servers, there is work to
> > fix up vger and move it over to the LF-managed infrastructure, perhaps
> > work with the vger admins to help that effort out?
>
> I'm pretty used to -stable patches going to l-k, so I got used to
> current workflow. OTOH ... -stable _is_ quite significant fraction of
> total lkml traffic, and I see how people may hate that.
>
> Is not it ultimately for vger admins to decide what kind of load they
> consider acceptable?
>
> Would it make sense to somehow batch the messages, or perhaps to
> modify patchbombing scripts to send patches "slowly" so that -stable
> does not DoS other lkml users?
>
> Actually, if the patch is same between multiple -stable releases
> (which is rather common case) sending it just once tagged with "this
> goes to 4.9, 4.14, 4.19 and 5.10" would both take less bandwidth and
> make review easier. (But I see it may not be that easy).
>
Hi Pavel,
I have to breakdown In-Reply-To chain.
I can't see the message you sent above on lore, so I had to "lei up"
in order to get it. On lore, the patch series thread [1] displayed
is until [1001/1157], and rest of the thread (including yours) is skipped.
Actually, I can see your message from search results [2].
I guess why more than a thousand of patches must be reviewed for this
stable review cycle is because many of them (which have stable list CCed)
are errorneously submitted and merged for 6.0 merge window, not as
stabilization fixes for 5.19. But I also wonder if any of these patches
are not actually qualified for stable (new drivers?).
[1]: https://lore.kernel.org/stable/20220815180439.416659447@linuxfoundation.org…
[2]: https://lore.kernel.org/stable/20220816115614.GB27428@duo.ucw.cz/
Thanks.
--
An old man doll... just what I always wanted! - Clara