* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
@ 2025-01-06 19:00 ` Naresh Kamboju
2025-01-09 11:39 ` Greg Kroah-Hartman
2025-01-06 20:04 ` Miguel Ojeda
` (11 subsequent siblings)
12 siblings, 1 reply; 18+ messages in thread
From: Naresh Kamboju @ 2025-01-06 19:00 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar, broonie, linux-i2c,
andi.shyti
On Mon, 6 Jan 2025 at 20:53, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
The following build errors were noticed while building the
allmodconfig builds on arm64 on the stable-rc linux-6.6.y
branch.
This is first seen on 5652330123c6a64b444f3012d9c9013742a872e7.
GOOD: v6.6.69
BAD: 5652330123c6a64b444f3012d9c9013742a872e7
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Build error:
============
drivers/i2c/busses/i2c-xgene-slimpro.c:95: error: "PCC_SIGNATURE"
redefined [-Werror]
95 | #define PCC_SIGNATURE 0x50424300
|
In file included from drivers/i2c/busses/i2c-xgene-slimpro.c:12:
include/acpi/pcc.h:23: note: this is the location of the previous definition
23 | #define PCC_SIGNATURE 0x50434300
|
cc1: all warnings being treated as errors
make[6]: *** [scripts/Makefile.build:243: drivers/i2c/busses/i2c-xgene
Links:
-------
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6/testrun/26613311/suite/build/test/gcc-13-allmodconfig/log
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6/testrun/26613311/suite/build/test/gcc-13-allmodconfig/details/
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6/testrun/26613311/suite/build/test/gcc-13-allmodconfig/history/
metadata:
----
git sha: 5652330123c6a64b444f3012d9c9013742a872e7
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
kernel config:
https://storage.tuxsuite.com/public/linaro/lkft/builds/2rGGBoqD6FxSfg6IKJLK43h9cCM/config
build url: https://storage.tuxsuite.com/public/linaro/lkft/builds/2rGGBoqD6FxSfg6IKJLK43h9cCM/
toolchain: clang, gcc-13, gcc-8
arch: arm64
config: allmodconfig
--
Linaro LKFT
https://lkft.linaro.org
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 19:00 ` Naresh Kamboju
@ 2025-01-09 11:39 ` Greg Kroah-Hartman
0 siblings, 0 replies; 18+ messages in thread
From: Greg Kroah-Hartman @ 2025-01-09 11:39 UTC (permalink / raw)
To: Naresh Kamboju
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar, broonie, linux-i2c,
andi.shyti
On Tue, Jan 07, 2025 at 12:30:26AM +0530, Naresh Kamboju wrote:
> On Mon, 6 Jan 2025 at 20:53, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.6.70 release.
> > There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> The following build errors were noticed while building the
> allmodconfig builds on arm64 on the stable-rc linux-6.6.y
> branch.
>
> This is first seen on 5652330123c6a64b444f3012d9c9013742a872e7.
> GOOD: v6.6.69
> BAD: 5652330123c6a64b444f3012d9c9013742a872e7
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Build error:
> ============
> drivers/i2c/busses/i2c-xgene-slimpro.c:95: error: "PCC_SIGNATURE"
> redefined [-Werror]
> 95 | #define PCC_SIGNATURE 0x50424300
> |
> In file included from drivers/i2c/busses/i2c-xgene-slimpro.c:12:
> include/acpi/pcc.h:23: note: this is the location of the previous definition
> 23 | #define PCC_SIGNATURE 0x50434300
> |
> cc1: all warnings being treated as errors
> make[6]: *** [scripts/Makefile.build:243: drivers/i2c/busses/i2c-xgene
Thanks, I've applied a patch to fix this up.
greg k-h
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
2025-01-06 19:00 ` Naresh Kamboju
@ 2025-01-06 20:04 ` Miguel Ojeda
2025-01-06 20:13 ` Florian Fainelli
` (10 subsequent siblings)
12 siblings, 0 replies; 18+ messages in thread
From: Miguel Ojeda @ 2025-01-06 20:04 UTC (permalink / raw)
To: gregkh
Cc: akpm, broonie, conor, f.fainelli, hargar, jonathanh, linux-kernel,
linux, lkft-triage, patches, patches, pavel, rwarsow, shuah, srw,
stable, sudipm.mukherjee, torvalds
On Mon, 06 Jan 2025 16:13:24 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +0000.
> Anything received after that time might be too late.
I got (in both the two runs I did):
[ 0.022989] ------------[ cut here ]------------
[ 0.023006] Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead
[ 0.023362] WARNING: CPU: 0 PID: 0 at mm/memblock.c:1325 memblock_set_node+0xcf/0xe0
[ 0.023841] Modules linked in:
[ 0.023988] CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.70-rc1-g5652330123c6 #1
[ 0.024062] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
[ 0.024156] RIP: 0010:memblock_set_node+0xcf/0xe0
[ 0.024215] Code: 2c 07 48 83 c0 18 48 ff c9 75 f0 48 89 df e8 78 01 00 00 31 c0 eb a8 c6 05 a7 24 a6 ff 01 48 c7 c7 1e 37 7b a7 e8 71 aa 07 fe <0f> 0b e9 67 ff ff ff e8 75 f3 e3 fe 0f 1f 44 00 00 55 41 57 41 56
[ 0.024361] RSP: 0000:ffffffffa7a03eb0 EFLAGS: 00000046 ORIG_RAX: 0000000000000000
[ 0.024386] RAX: 0000000000000000 RBX: ffffffffa82a2240 RCX: ffffffffa7a52068
[ 0.024397] RDX: ffffffffa7a03daf RSI: 0000000000000082 RDI: ffffffffa7a52060
[ 0.024407] RBP: 0000000000000000 R08: ffffffffa7a52240 R09: 4f4e5f414d554e20
[ 0.024417] R10: 2045444f4e5f4f4e R11: 0a64616574736e69 R12: 0000000000000040
[ 0.024428] R13: 0000000000000000 R14: ffffffffffffffff R15: 0000000000000000
[ 0.024465] FS: 0000000000000000(0000) GS:ffffffffa81a4000(0000) knlGS:0000000000000000
[ 0.024490] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.024502] CR2: ffff8c88c6001000 CR3: 0000000005628000 CR4: 00000000000000b0
[ 0.024585] Call Trace:
[ 0.024778] <TASK>
[ 0.024953] ? __warn+0xc3/0x1c0
[ 0.025012] ? memblock_set_node+0xcf/0xe0
[ 0.025024] ? report_bug+0x144/0x1e0
[ 0.025042] ? early_fixup_exception+0x46/0x90
[ 0.025051] ? early_idt_handler_common+0x2f/0x40
[ 0.025065] ? memblock_set_node+0xcf/0xe0
[ 0.025074] ? acpi_numa_processor_affinity_init+0x80/0x80
[ 0.025084] ? numa_init+0x5e/0x190
[ 0.025091] ? x86_numa_init+0x15/0x40
[ 0.025099] ? setup_arch+0x4a3/0x5a0
[ 0.025105] ? start_kernel+0x5a/0x3a0
[ 0.025115] ? x86_64_start_reservations+0x20/0x20
[ 0.025122] ? x86_64_start_kernel+0xa7/0xb0
[ 0.025128] ? secondary_startup_64_no_verify+0x179/0x17b
[ 0.025156] </TASK>
[ 0.025196] ---[ end trace 0000000000000000 ]---
I hope the helps!
Cheers,
Miguel
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
2025-01-06 19:00 ` Naresh Kamboju
2025-01-06 20:04 ` Miguel Ojeda
@ 2025-01-06 20:13 ` Florian Fainelli
2025-01-07 0:36 ` Peter Schneider
` (9 subsequent siblings)
12 siblings, 0 replies; 18+ messages in thread
From: Florian Fainelli @ 2025-01-06 20:13 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, sudipm.mukherjee, srw, rwarsow,
conor, hargar, broonie
On 1/6/25 07:13, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on
BMIPS_GENERIC:
Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (2 preceding siblings ...)
2025-01-06 20:13 ` Florian Fainelli
@ 2025-01-07 0:36 ` Peter Schneider
2025-01-07 1:16 ` Peter Schneider
2025-01-07 0:54 ` SeongJae Park
` (8 subsequent siblings)
12 siblings, 1 reply; 18+ messages in thread
From: Peter Schneider @ 2025-01-07 0:36 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor, hargar, broonie
Am 06.01.2025 um 16:13 schrieb Greg Kroah-Hartman:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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.
6.6.70-rc1 builds, boots and seems to work on my 2-socket Ivy Bridge Xeon E5-2697 v2
server, but I see a scary looking dmesg warning, right after booting. As it is currently
running, I will try building 6.12.9-rc with it, and see how that goes. The dmesg warnings
I see look similar to that already reported by Miguel Ojeda.
[ 0.012910] ACPI: Reserving ERST table memory at [mem 0x7cca41c8-0x7cca43f7]
[ 0.012911] ACPI: Reserving HEST table memory at [mem 0x7cca43f8-0x7cca449f]
[ 0.012912] ACPI: Reserving BERT table memory at [mem 0x7cca44a0-0x7cca44cf]
[ 0.012938] ------------[ cut here ]------------
[ 0.012939] Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead
[ 0.012948] WARNING: CPU: 0 PID: 0 at mm/memblock.c:1324 memblock_set_node+0x10c/0x120
[ 0.012955] Modules linked in:
[ 0.012956] CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.70-rc1+ #1
[ 0.012959] Hardware name: ASUSTeK COMPUTER INC. Z9PE-D16 Series/Z9PE-D16 Series, BIOS
5601 06/11/2015
[ 0.012960] RIP: 0010:memblock_set_node+0x10c/0x120
[ 0.012962] Code: 0f 87 fe c0 ca 00 41 83 e4 01 74 0b 41 bc ff ff ff ff e9 50 ff ff ff
48 c7 c7 d0 28 fa 98 c6 05 58 0a 13 02 01 e8 14 86 ce ff <0f> 0b eb de e8 fb e3 d0 00 66
66 2e 0f 1f 84 00 00 00 00 00 90 90
[ 0.012965] RSP: 0000:ffffffff99803df8 EFLAGS: 00010046 ORIG_RAX: 0000000000000000
[ 0.012967] RAX: 0000000000000000 RBX: ffffffff999fc990 RCX: 0000000000000000
[ 0.012969] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 0.012970] RBP: ffffffff99803e28 R08: 0000000000000000 R09: 0000000000000000
[ 0.012971] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 0.012972] R13: 0000000000000000 R14: ffffffffffffffff R15: 000000000008a000
[ 0.012973] FS: 0000000000000000(0000) GS:ffffffff99bb0000(0000) knlGS:0000000000000000
[ 0.012975] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.012976] CR2: ffff9e62eac01000 CR3: 0000000ae9e36000 CR4: 00000000000200f0
[ 0.012978] Call Trace:
[ 0.012979] <TASK>
[ 0.012981] ? show_regs+0x6d/0x80
[ 0.012987] ? __warn+0x89/0x160
[ 0.012990] ? memblock_set_node+0x10c/0x120
[ 0.012993] ? report_bug+0x17e/0x1b0
[ 0.012996] ? fixup_exception+0x27/0x370
[ 0.013000] ? early_fixup_exception+0x9b/0xf0
[ 0.013004] ? do_early_exception+0x25/0x80
[ 0.013008] ? early_idt_handler_common+0x2f/0x3a
[ 0.013013] ? memblock_set_node+0x10c/0x120
[ 0.013015] ? memblock_set_node+0x10c/0x120
[ 0.013017] ? __pfx_x86_acpi_numa_init+0x10/0x10
[ 0.013021] numa_init+0x82/0x570
[ 0.013025] x86_numa_init+0x1f/0x60
[ 0.013028] initmem_init+0xe/0x20
[ 0.013030] setup_arch+0x98b/0xea0
[ 0.013034] start_kernel+0x6c/0xb00
[ 0.013039] ? load_ucode_intel_bsp+0x3d/0x80
[ 0.013044] x86_64_start_reservations+0x18/0x30
[ 0.013046] x86_64_start_kernel+0xbf/0x110
[ 0.013049] secondary_startup_64_no_verify+0x18f/0x19b
[ 0.013056] </TASK>
[ 0.013057] ---[ end trace 0000000000000000 ]---
[ 0.013063] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[ 0.013065] SRAT: PXM 0 -> APIC 0x01 -> Node 0
[ 0.013066] SRAT: PXM 0 -> APIC 0x02 -> Node 0
[ 0.013066] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-07 0:36 ` Peter Schneider
@ 2025-01-07 1:16 ` Peter Schneider
0 siblings, 0 replies; 18+ messages in thread
From: Peter Schneider @ 2025-01-07 1:16 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor, hargar, broonie
[-- Attachment #1.1: Type: text/plain, Size: 1457 bytes --]
Am 07.01.2025 um 01:36 schrieb Peter Schneider:
> Am 06.01.2025 um 16:13 schrieb Greg Kroah-Hartman:
>> This is the start of the stable review cycle for the 6.6.70 release.
>> There are 222 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.
>
> 6.6.70-rc1 builds, boots and seems to work on my 2-socket Ivy Bridge Xeon E5-2697 v2
> server, but I see a scary looking dmesg warning, right after booting. As it is currently
> running, I will try building 6.12.9-rc with it, and see how that goes. The dmesg warnings
> I see look similar to that already reported by Miguel Ojeda.
[...]
So running 6.6.70-rc1, despite the above mentioned initial warning message, I could build
6.12.9-rc1 just fine with it. It took the usual ~20 minutes, and no more dmesgs warning
have been added.
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (3 preceding siblings ...)
2025-01-07 0:36 ` Peter Schneider
@ 2025-01-07 0:54 ` SeongJae Park
2025-01-07 7:03 ` Ron Economos
` (7 subsequent siblings)
12 siblings, 0 replies; 18+ messages in thread
From: SeongJae Park @ 2025-01-07 0:54 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: SeongJae Park, stable, patches, linux-kernel, torvalds, akpm,
linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar, broonie, damon
Hello,
On Mon, 6 Jan 2025 16:13:24 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +0000.
> Anything received after that time might be too late.
This rc kernel passes DAMON functionality test[1] on my test machine.
Attaching the test results summary below. Please note that I retrieved the
kernel from linux-stable-rc tree[2].
Tested-by: SeongJae Park <sj@kernel.org>
[1] https://github.com/damonitor/damon-tests/tree/next/corr
[2] 5652330123c6 ("Linux 6.6.70-rc1")
Thanks,
SJ
[...]
---
ok 1 selftests: damon: debugfs_attrs.sh # SKIP
ok 2 selftests: damon: debugfs_schemes.sh # SKIP
ok 3 selftests: damon: debugfs_target_ids.sh # SKIP
ok 4 selftests: damon: debugfs_empty_targets.sh # SKIP
ok 5 selftests: damon: debugfs_huge_count_read_write.sh # SKIP
ok 6 selftests: damon: debugfs_duplicate_context_creation.sh # SKIP
ok 7 selftests: damon: debugfs_rm_non_contexts.sh # SKIP
ok 8 selftests: damon: sysfs.sh
ok 9 selftests: damon: sysfs_update_removed_scheme_dir.sh
ok 10 selftests: damon: reclaim.sh
ok 11 selftests: damon: lru_sort.sh
ok 1 selftests: damon-tests: kunit.sh
ok 2 selftests: damon-tests: huge_count_read_write.sh # SKIP
ok 3 selftests: damon-tests: buffer_overflow.sh
ok 4 selftests: damon-tests: rm_contexts.sh # SKIP
ok 5 selftests: damon-tests: record_null_deref.sh
ok 6 selftests: damon-tests: dbgfs_target_ids_read_before_terminate_race.sh
ok 7 selftests: damon-tests: dbgfs_target_ids_pid_leak.sh
ok 8 selftests: damon-tests: damo_tests.sh
ok 9 selftests: damon-tests: masim-record.sh
ok 10 selftests: damon-tests: build_i386.sh
ok 11 selftests: damon-tests: build_arm64.sh # SKIP
ok 12 selftests: damon-tests: build_m68k.sh # SKIP
ok 13 selftests: damon-tests: build_i386_idle_flag.sh
ok 14 selftests: damon-tests: build_i386_highpte.sh
ok 15 selftests: damon-tests: build_nomemcg.sh
PASS
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (4 preceding siblings ...)
2025-01-07 0:54 ` SeongJae Park
@ 2025-01-07 7:03 ` Ron Economos
2025-01-07 10:24 ` Naresh Kamboju
` (6 subsequent siblings)
12 siblings, 0 replies; 18+ messages in thread
From: Ron Economos @ 2025-01-07 7:03 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor, hargar, broonie
On 1/6/25 07:13, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Tested-by: Ron Economos <re@w6rz.net>
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (5 preceding siblings ...)
2025-01-07 7:03 ` Ron Economos
@ 2025-01-07 10:24 ` Naresh Kamboju
2025-01-07 13:01 ` Mike Rapoport
2025-01-07 12:33 ` Mark Brown
` (5 subsequent siblings)
12 siblings, 1 reply; 18+ messages in thread
From: Naresh Kamboju @ 2025-01-07 10:24 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar, broonie,
Jan Beulich, Mike Rapoport
On Mon, 6 Jan 2025 at 20:53, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
As others have reported, boot warnings on x86 have been noticed
memblock: make memblock_set_node() also warn about use of MAX_NUMNODES
[ Upstream commit e0eec24e2e199873f43df99ec39773ad3af2bff7 ]
diff --git a/mm/memblock.c b/mm/memblock.c
index 87a2b4340ce4ea..ba64b47b7c3b24 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -1321,6 +1321,10 @@ int __init_memblock
memblock_set_node(phys_addr_t base, phys_addr_t size,
int start_rgn, end_rgn;
int i, ret;
+ if (WARN_ONCE(nid == MAX_NUMNODES,
+ "Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead\n"))
+ nid = NUMA_NO_NODE;
+
ret = memblock_isolate_range(type, base, size, &start_rgn, &end_rgn);
if (ret)
return ret;
--
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
------------[ cut here ]------------
[ 0.042522] Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead
[ 0.043058] WARNING: CPU: 0 PID: 0 at mm/memblock.c:1324
memblock_set_node+0xf0/0x100
[ 0.043730] Modules linked in:
[ 0.043957] CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.70-rc1 #1
[ 0.044026] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),
BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 0.044174] RIP: 0010:memblock_set_node+0xf0/0x100
[ 0.044293] Code: 3d 81 da ef ff 00 74 0b 41 bc ff ff ff ff e9 6c
ff ff ff 48 c7 c7 30 40 e3 8e 48 89 75 d0 c6 05 62 da ef ff 01 e8 20
cb 04 fe <0f> 0b 48 8b 75 d0 eb d6 e8 43 db 0e ff 0f 1f 00 90 90 90 90
90 90
[ 0.044494] RSP: 0000:ffffffff8f003e08 EFLAGS: 00010082 ORIG_RAX:
0000000000000000
[ 0.044537] RAX: 0000000000000000 RBX: ffffffff8f46da30 RCX: 0000000000000000
[ 0.044553] RDX: ffffffff8f156f08 RSI: 0000000000000082 RDI: 0000000000000001
[ 0.044588] RBP: ffffffff8f003e38 R08: 0000000000000000 R09: 4f4e5f414d554e20
[ 0.044606] R10: 2045444f4e5f4f4e R11: 0a64616574736e69 R12: 0000000000000040
[ 0.044621] R13: 0000000000000000 R14: 000000013ee00000 R15: 0000000000014750
[ 0.044673] FS: 0000000000000000(0000) GS:ffffffff8f347000(0000)
knlGS:0000000000000000
[ 0.044707] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.044723] CR2: ffff9ab33ffff000 CR3: 0000000140c44000 CR4: 00000000000000b0
[ 0.044816] Call Trace:
[ 0.045237] <TASK>
[ 0.045521] ? show_regs+0x69/0x80
[ 0.045593] ? __warn+0x8d/0x150
[ 0.045611] ? memblock_set_node+0xf0/0x100
[ 0.045629] ? report_bug+0x171/0x1a0
[ 0.045648] ? fixup_exception+0x2b/0x310
[ 0.045669] ? early_fixup_exception+0xb3/0xd0
[ 0.045687] ? do_early_exception+0x1f/0x60
[ 0.045716] ? early_idt_handler_common+0x2f/0x40
[ 0.045742] ? memblock_set_node+0xf0/0x100
[ 0.045760] ? memblock_set_node+0xf0/0x100
[ 0.045792] ? __pfx_x86_acpi_numa_init+0x10/0x10
[ 0.045817] numa_init+0x8b/0x600
[ 0.045932] x86_numa_init+0x23/0x50
[ 0.045953] initmem_init+0x12/0x20
[ 0.045969] setup_arch+0x88b/0xce0
[ 0.045988] start_kernel+0x76/0x6d0
[ 0.046008] x86_64_start_reservations+0x1c/0x30
[ 0.046022] x86_64_start_kernel+0xca/0xe0
[ 0.046037] secondary_startup_64_no_verify+0x178/0x17b
[ 0.046111] </TASK>
[ 0.046180] ---[ end trace 0000000000000000 ]---
Links:
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6/testrun/26599367/suite/log-parser-boot/tests/
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6/testrun/26599367/suite/log-parser-boot/test/exception-usage-of-max_numnodes-is-deprecated-use-numa_no_node-instead/log
## Build
* kernel: 6.6.70-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git commit: 5652330123c6a64b444f3012d9c9013742a872e7
* git describe: v6.6.69-223-g5652330123c6
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6
## Test Regressions (compared to v6.6.68-87-g159cc5fd9b13)
* arm64, build
- clang-19-allmodconfig
- clang-19-allyesconfig
- gcc-13-allmodconfig
- gcc-13-allyesconfig
## Metric Regressions (compared to v6.6.68-87-g159cc5fd9b13)
## Test Fixes (compared to v6.6.68-87-g159cc5fd9b13)
## Metric Fixes (compared to v6.6.68-87-g159cc5fd9b13)
## Test result summary
total: 150166, pass: 122611, fail: 4998, skip: 22391, xfail: 166
## Build Summary
* arc: 6 total, 5 passed, 1 failed
* arm: 132 total, 132 passed, 0 failed
* arm64: 44 total, 38 passed, 6 failed
* i386: 31 total, 28 passed, 3 failed
* mips: 30 total, 25 passed, 5 failed
* parisc: 5 total, 5 passed, 0 failed
* powerpc: 36 total, 32 passed, 4 failed
* riscv: 23 total, 22 passed, 1 failed
* s390: 18 total, 14 passed, 4 failed
* sh: 12 total, 10 passed, 2 failed
* sparc: 9 total, 8 passed, 1 failed
* x86_64: 36 total, 35 passed, 1 failed
## Test suites summary
* boot
* commands
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-efivarfs
* kselftest-exec
* kselftest-filesystems
* kselftest-filesystems-binderfs
* kselftest-filesystems-epoll
* kselftest-firmware
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-kcmp
* kselftest-kvm
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-mincore
* kselftest-mqueue
* kselftest-net
* kselftest-net-mptcp
* kselftest-openat2
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-tc-testing
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user_events
* kselftest-vDSO
* kselftest-x86
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-build-clang
* log-parser-build-gcc
* log-parser-test
* ltp-capability
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-hugetlb
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* perf
* rcutorture
--
Linaro LKFT
https://lkft.linaro.org
^ permalink raw reply related [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-07 10:24 ` Naresh Kamboju
@ 2025-01-07 13:01 ` Mike Rapoport
2025-01-09 11:52 ` Greg Kroah-Hartman
0 siblings, 1 reply; 18+ messages in thread
From: Mike Rapoport @ 2025-01-07 13:01 UTC (permalink / raw)
To: Naresh Kamboju
Cc: Greg Kroah-Hartman, stable, patches, linux-kernel, torvalds, akpm,
linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar, broonie,
Jan Beulich
On Tue, Jan 07, 2025 at 03:54:43PM +0530, Naresh Kamboju wrote:
> On Mon, 6 Jan 2025 at 20:53, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.6.70 release.
> > There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
>
> As others have reported, boot warnings on x86 have been noticed
>
> memblock: make memblock_set_node() also warn about use of MAX_NUMNODES
> [ Upstream commit e0eec24e2e199873f43df99ec39773ad3af2bff7 ]
There's 8043832e2a12 ("memblock: use numa_valid_node() helper to check for
invalid node ID") that fixes it
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 87a2b4340ce4ea..ba64b47b7c3b24 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -1321,6 +1321,10 @@ int __init_memblock
> memblock_set_node(phys_addr_t base, phys_addr_t size,
> int start_rgn, end_rgn;
> int i, ret;
>
> + if (WARN_ONCE(nid == MAX_NUMNODES,
> + "Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead\n"))
> + nid = NUMA_NO_NODE;
> +
> ret = memblock_isolate_range(type, base, size, &start_rgn, &end_rgn);
> if (ret)
> return ret;
> --
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ------------[ cut here ]------------
> [ 0.042522] Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead
> [ 0.043058] WARNING: CPU: 0 PID: 0 at mm/memblock.c:1324
> memblock_set_node+0xf0/0x100
> [ 0.043730] Modules linked in:
> [ 0.043957] CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.70-rc1 #1
> [ 0.044026] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),
> BIOS 1.16.3-debian-1.16.3-2 04/01/2014
> [ 0.044174] RIP: 0010:memblock_set_node+0xf0/0x100
> [ 0.044293] Code: 3d 81 da ef ff 00 74 0b 41 bc ff ff ff ff e9 6c
> ff ff ff 48 c7 c7 30 40 e3 8e 48 89 75 d0 c6 05 62 da ef ff 01 e8 20
> cb 04 fe <0f> 0b 48 8b 75 d0 eb d6 e8 43 db 0e ff 0f 1f 00 90 90 90 90
> 90 90
> [ 0.044494] RSP: 0000:ffffffff8f003e08 EFLAGS: 00010082 ORIG_RAX:
> 0000000000000000
> [ 0.044537] RAX: 0000000000000000 RBX: ffffffff8f46da30 RCX: 0000000000000000
> [ 0.044553] RDX: ffffffff8f156f08 RSI: 0000000000000082 RDI: 0000000000000001
> [ 0.044588] RBP: ffffffff8f003e38 R08: 0000000000000000 R09: 4f4e5f414d554e20
> [ 0.044606] R10: 2045444f4e5f4f4e R11: 0a64616574736e69 R12: 0000000000000040
> [ 0.044621] R13: 0000000000000000 R14: 000000013ee00000 R15: 0000000000014750
> [ 0.044673] FS: 0000000000000000(0000) GS:ffffffff8f347000(0000)
> knlGS:0000000000000000
> [ 0.044707] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 0.044723] CR2: ffff9ab33ffff000 CR3: 0000000140c44000 CR4: 00000000000000b0
> [ 0.044816] Call Trace:
> [ 0.045237] <TASK>
> [ 0.045521] ? show_regs+0x69/0x80
> [ 0.045593] ? __warn+0x8d/0x150
> [ 0.045611] ? memblock_set_node+0xf0/0x100
> [ 0.045629] ? report_bug+0x171/0x1a0
> [ 0.045648] ? fixup_exception+0x2b/0x310
> [ 0.045669] ? early_fixup_exception+0xb3/0xd0
> [ 0.045687] ? do_early_exception+0x1f/0x60
> [ 0.045716] ? early_idt_handler_common+0x2f/0x40
> [ 0.045742] ? memblock_set_node+0xf0/0x100
> [ 0.045760] ? memblock_set_node+0xf0/0x100
> [ 0.045792] ? __pfx_x86_acpi_numa_init+0x10/0x10
> [ 0.045817] numa_init+0x8b/0x600
> [ 0.045932] x86_numa_init+0x23/0x50
> [ 0.045953] initmem_init+0x12/0x20
> [ 0.045969] setup_arch+0x88b/0xce0
> [ 0.045988] start_kernel+0x76/0x6d0
> [ 0.046008] x86_64_start_reservations+0x1c/0x30
> [ 0.046022] x86_64_start_kernel+0xca/0xe0
> [ 0.046037] secondary_startup_64_no_verify+0x178/0x17b
> [ 0.046111] </TASK>
> [ 0.046180] ---[ end trace 0000000000000000 ]---
>
> Links:
> - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6/testrun/26599367/suite/log-parser-boot/tests/
> - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6/testrun/26599367/suite/log-parser-boot/test/exception-usage-of-max_numnodes-is-deprecated-use-numa_no_node-instead/log
>
> ## Build
> * kernel: 6.6.70-rc1
> * git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> * git commit: 5652330123c6a64b444f3012d9c9013742a872e7
> * git describe: v6.6.69-223-g5652330123c6
> * test details:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.6.y/build/v6.6.69-223-g5652330123c6
>
> ## Test Regressions (compared to v6.6.68-87-g159cc5fd9b13)
> * arm64, build
> - clang-19-allmodconfig
> - clang-19-allyesconfig
> - gcc-13-allmodconfig
> - gcc-13-allyesconfig
>
> ## Metric Regressions (compared to v6.6.68-87-g159cc5fd9b13)
>
> ## Test Fixes (compared to v6.6.68-87-g159cc5fd9b13)
>
> ## Metric Fixes (compared to v6.6.68-87-g159cc5fd9b13)
>
> ## Test result summary
> total: 150166, pass: 122611, fail: 4998, skip: 22391, xfail: 166
>
> ## Build Summary
> * arc: 6 total, 5 passed, 1 failed
> * arm: 132 total, 132 passed, 0 failed
> * arm64: 44 total, 38 passed, 6 failed
> * i386: 31 total, 28 passed, 3 failed
> * mips: 30 total, 25 passed, 5 failed
> * parisc: 5 total, 5 passed, 0 failed
> * powerpc: 36 total, 32 passed, 4 failed
> * riscv: 23 total, 22 passed, 1 failed
> * s390: 18 total, 14 passed, 4 failed
> * sh: 12 total, 10 passed, 2 failed
> * sparc: 9 total, 8 passed, 1 failed
> * x86_64: 36 total, 35 passed, 1 failed
>
> ## Test suites summary
> * boot
> * commands
> * kselftest-arm64
> * kselftest-breakpoints
> * kselftest-capabilities
> * kselftest-cgroup
> * kselftest-clone3
> * kselftest-core
> * kselftest-cpu-hotplug
> * kselftest-cpufreq
> * kselftest-efivarfs
> * kselftest-exec
> * kselftest-filesystems
> * kselftest-filesystems-binderfs
> * kselftest-filesystems-epoll
> * kselftest-firmware
> * kselftest-fpu
> * kselftest-ftrace
> * kselftest-futex
> * kselftest-gpio
> * kselftest-intel_pstate
> * kselftest-ipc
> * kselftest-kcmp
> * kselftest-kvm
> * kselftest-livepatch
> * kselftest-membarrier
> * kselftest-memfd
> * kselftest-mincore
> * kselftest-mqueue
> * kselftest-net
> * kselftest-net-mptcp
> * kselftest-openat2
> * kselftest-ptrace
> * kselftest-rseq
> * kselftest-rtc
> * kselftest-seccomp
> * kselftest-sigaltstack
> * kselftest-size
> * kselftest-tc-testing
> * kselftest-timers
> * kselftest-tmpfs
> * kselftest-tpm2
> * kselftest-user_events
> * kselftest-vDSO
> * kselftest-x86
> * kunit
> * kvm-unit-tests
> * libgpiod
> * libhugetlbfs
> * log-parser-boot
> * log-parser-build-clang
> * log-parser-build-gcc
> * log-parser-test
> * ltp-capability
> * ltp-commands
> * ltp-containers
> * ltp-controllers
> * ltp-cpuhotplug
> * ltp-crypto
> * ltp-cve
> * ltp-dio
> * ltp-fcntl-locktests
> * ltp-filecaps
> * ltp-fs
> * ltp-fs_bind
> * ltp-fs_perms_simple
> * ltp-hugetlb
> * ltp-ipc
> * ltp-math
> * ltp-mm
> * ltp-nptl
> * ltp-pty
> * ltp-sched
> * ltp-smoke
> * ltp-syscalls
> * ltp-tracing
> * perf
> * rcutorture
>
> --
> Linaro LKFT
> https://lkft.linaro.org
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-07 13:01 ` Mike Rapoport
@ 2025-01-09 11:52 ` Greg Kroah-Hartman
0 siblings, 0 replies; 18+ messages in thread
From: Greg Kroah-Hartman @ 2025-01-09 11:52 UTC (permalink / raw)
To: Mike Rapoport
Cc: Naresh Kamboju, stable, patches, linux-kernel, torvalds, akpm,
linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar, broonie,
Jan Beulich
On Tue, Jan 07, 2025 at 03:01:56PM +0200, Mike Rapoport wrote:
> On Tue, Jan 07, 2025 at 03:54:43PM +0530, Naresh Kamboju wrote:
> > On Mon, 6 Jan 2025 at 20:53, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > This is the start of the stable review cycle for the 6.6.70 release.
> > > There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> >
> > As others have reported, boot warnings on x86 have been noticed
> >
> > memblock: make memblock_set_node() also warn about use of MAX_NUMNODES
> > [ Upstream commit e0eec24e2e199873f43df99ec39773ad3af2bff7 ]
>
> There's 8043832e2a12 ("memblock: use numa_valid_node() helper to check for
> invalid node ID") that fixes it
Thanks. I'll drop the offending commit for now and then add this, and
the fix, back in for the next round of -rc releases to get testing on
it.
greg k-h
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (6 preceding siblings ...)
2025-01-07 10:24 ` Naresh Kamboju
@ 2025-01-07 12:33 ` Mark Brown
2025-01-07 12:44 ` Jon Hunter
` (4 subsequent siblings)
12 siblings, 0 replies; 18+ messages in thread
From: Mark Brown @ 2025-01-07 12:33 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
On Mon, Jan 06, 2025 at 04:13:24PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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.
Tested-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (7 preceding siblings ...)
2025-01-07 12:33 ` Mark Brown
@ 2025-01-07 12:44 ` Jon Hunter
2025-01-07 21:20 ` [PATCH 6.6] " Hardik Garg
` (3 subsequent siblings)
12 siblings, 0 replies; 18+ messages in thread
From: Jon Hunter @ 2025-01-07 12:44 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: Greg Kroah-Hartman, patches, linux-kernel, torvalds, akpm, linux,
shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar, broonie,
linux-tegra, stable
On Mon, 06 Jan 2025 16:13:24 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
All tests passing for Tegra ...
Test results for stable-v6.6:
10 builds: 10 pass, 0 fail
26 boots: 26 pass, 0 fail
116 tests: 116 pass, 0 fail
Linux version: 6.6.70-rc1-g5652330123c6
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra20-ventana, tegra210-p2371-2180,
tegra210-p3450-0000, tegra30-cardhu-a04
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Jon
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (8 preceding siblings ...)
2025-01-07 12:44 ` Jon Hunter
@ 2025-01-07 21:20 ` Hardik Garg
2025-01-07 23:15 ` [PATCH 6.6 000/222] " Shuah Khan
` (2 subsequent siblings)
12 siblings, 0 replies; 18+ messages in thread
From: Hardik Garg @ 2025-01-07 21:20 UTC (permalink / raw)
To: gregkh
Cc: akpm, broonie, conor, f.fainelli, hargar, jonathanh, linux-kernel,
linux, lkft-triage, patches, patches, pavel, rwarsow, shuah, srw,
stable, sudipm.mukherjee, torvalds
The kernel, bpf tool, amd kselftest tool builds fine for v6.6.70-rc1 on x86 and arm64 Azure VM.
Tested-by: Hardik Garg <hargar@linux.microsoft.com>
Thanks,
Hardik
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (9 preceding siblings ...)
2025-01-07 21:20 ` [PATCH 6.6] " Hardik Garg
@ 2025-01-07 23:15 ` Shuah Khan
2025-01-08 12:27 ` Muhammad Usama Anjum
2025-01-08 14:12 ` Harshit Mogalapalli
12 siblings, 0 replies; 18+ messages in thread
From: Shuah Khan @ 2025-01-07 23:15 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor, hargar, broonie, Shuah Khan
On 1/6/25 08:13, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (10 preceding siblings ...)
2025-01-07 23:15 ` [PATCH 6.6 000/222] " Shuah Khan
@ 2025-01-08 12:27 ` Muhammad Usama Anjum
2025-01-08 14:12 ` Harshit Mogalapalli
12 siblings, 0 replies; 18+ messages in thread
From: Muhammad Usama Anjum @ 2025-01-08 12:27 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: Usama.Anjum, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, hargar, broonie
On 1/6/25 8:13 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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 Wed, 08 Jan 2025 15:11:04 +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.6.70-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.6.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
> -------------
OVERVIEW
Builds: 38 passed, 3 failed
Boot tests: 358 passed, 0 failed
CI systems: broonie, maestro
REVISION
Commit
name: v6.6.69-223-g5652330123c6
hash: 5652330123c6a64b444f3012d9c9013742a872e7
Checked out from
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y
BUILDS
Failures
-x86_64 (cros://chromeos-6.6/x86_64/chromeos-intel-pineview.flavour.config)
Build detail: https://kcidb.kernelci.org/d/build/build?orgId=1&var-id=maestro:677c10a0423acf18d2737e91
Build error: ld: kernel/kexec_core.o: in function `__crash_kexec':
-arm64 (defconfig+allmodconfig)
Build detail: https://kcidb.kernelci.org/d/build/build?orgId=1&var-id=maestro:677c10aa423acf18d2737f1a
Build error: drivers/i2c/busses/i2c-xgene-slimpro.c:95:9: error: 'PCC_SIGNATURE' macro redefined [-Werror,-Wmacro-redefined]
-x86_64 (cros://chromeos-6.6/x86_64/chromeos-amd-stoneyridge.flavour.config)
Build detail: https://kcidb.kernelci.org/d/build/build?orgId=1&var-id=maestro:677c109b423acf18d2737e5a
Build error: ld: kernel/kexec_core.o: in function `__crash_kexec':
CI system: maestro
BOOT TESTS
No failure found
See complete and up-to-date report at:
https://kcidb.kernelci.org/d/revision/revision?orgId=1&var-git_commit_hash=5652330123c6a64b444f3012d9c9013742a872e7&var-patchset_hash=
Tested-by: kernelci.org bot <bot@kernelci.org>
Thanks,
KernelCI team
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
` (11 preceding siblings ...)
2025-01-08 12:27 ` Muhammad Usama Anjum
@ 2025-01-08 14:12 ` Harshit Mogalapalli
12 siblings, 0 replies; 18+ messages in thread
From: Harshit Mogalapalli @ 2025-01-08 14:12 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor, hargar, broonie, Vegard Nossum, Darren Kenny
Hi Greg,
On 06/01/25 20:43, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 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.
No problems seen on x86_64 and aarch64 with our testing.
Tested-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Thanks,
Harshit
^ permalink raw reply [flat|nested] 18+ messages in thread