On Thu, Oct 05, 2023 at 08:25:02PM +0530, Naresh Kamboju wrote: > On Thu, 5 Oct 2023 at 11:05, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > > > On Wed, 4 Oct 2023 at 23:53, Greg Kroah-Hartman > > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > This is the start of the stable review cycle for the 6.5.6 release. > > > There are 321 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 Fri, 06 Oct 2023 17:51:12 +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/v6.x/stable-review/patch-6.5.6-rc1.gz > > > or in the git tree and branch at: > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.5.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > The following kernel warning was noticed on qemu-armv7 while booting > > with kselftest merge configs enabled build on stable-rc 6.5.6-rc1. > > > > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx> > > > > > Hou Tao <houtao1@xxxxxxxxxx> > > > bpf: Ensure unit_size is matched with slab cache object size > > > > > > bpf: Ensure unit_size is matched with slab cache object size > > [ Upstream commit c930472552022bd09aab3cd946ba3f243070d5c7 ] > > > > [ 2.525383] ------------[ cut here ]------------ > > [ 2.525743] WARNING: CPU: 0 PID: 1 at kernel/bpf/memalloc.c:385 > > bpf_mem_alloc_init+0x3b0/0x3b4 > > [ 2.527241] bpf_mem_cache[0]: unexpected object size 128, expect 96 > > > Anders investigated this report and picked up the following patches to > solve the reported problem. > > d52b59315bf5e bpf: Adjust size_index according to the value of KMALLOC_MIN_SIZE > b1d53958b6931 bpf: Don't prefill for unused bpf_mem_cache > c930472552022 bpf: Ensure unit_size is matched with slab cache object size Those do not all apply cleanly to the tree, so I've dropped the one offending commit instead for 6.5.y and 6.1.y. thanks, greg k-h
