* Re: Linux 6.12-rc1
2024-09-29 22:51 Linux 6.12-rc1 Linus Torvalds
@ 2024-09-30 0:38 ` Guenter Roeck
2024-09-30 13:15 ` Jason A. Donenfeld
` (2 subsequent siblings)
3 siblings, 0 replies; 9+ messages in thread
From: Guenter Roeck @ 2024-09-30 0:38 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Sun, Sep 29, 2024 at 03:51:43PM -0700, Linus Torvalds wrote:
> So two weeks have passed, and rc1 is out - the merge window is closed.
>
> Despite conference travel (both for me and several maintainers),
> things seemed to go mostly fairly normally. There's a couple of
> notable new features in here: For one thing, PREEMPT_RT is now
> mainlined and enabled as a config option (you do need to enable
> "EXPERT" to get the question). For another, sched_ext also got merged.
>
> That said, the bulk is - as always - all the plain old regular
> updates, and that obviously means drivers dominate. We've got about
> 55% of the patch being drivers (and another 5% if you count the dts
> files). Add in 5% doc updates, and 10% tooling (mostly perf and
> selftests).
>
> That leaves about a quarter of the overall changes as core kernel
> code, split between arch updates, filesystems (yes, bcachefs, but also
> btrfs, smb sever and client, netfs updates, xfs and finally core VFS
> updates mostly in the form of 'struct fd' re-organisational cleanups).
> And MM, core networking, Rust, security layer updates etc.
>
> A little bit of everything, in other words. And nothing really looks
> all that strange. As always, the summary below is just the log of my
> merges, there's too much to list individually (some stats: 11k+
> regular commits, 850+ merges, 1700+ different authors).
>
> Let's get the testing and calming down period started, ok?
>
Fails to build on big endian systems. I'll send a patch in a minute.
Guenter
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Linux 6.12-rc1
2024-09-29 22:51 Linux 6.12-rc1 Linus Torvalds
2024-09-30 0:38 ` Guenter Roeck
@ 2024-09-30 13:15 ` Jason A. Donenfeld
2024-09-30 17:22 ` Linus Torvalds
2024-09-30 14:53 ` Build regressions/improvements in v6.12-rc1 Geert Uytterhoeven
2024-09-30 17:01 ` Linux 6.12-rc1 Guenter Roeck
3 siblings, 1 reply; 9+ messages in thread
From: Jason A. Donenfeld @ 2024-09-30 13:15 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
Pushed 5.12-rc1 too? Odd.
+ git fetch linus remote: Enumerating objects: 54527, done. remote: Counting objects: 100% (24190/24190), done. remote: Compressing objects: 100% (314/314), done.
remote: Total 54527 (delta 24053), reused 23963 (delta 23876), pack-reused 30337 Receiving objects: 100% (54527/54527), 34.39 MiB | 2.53 MiB/s, done. Resolving deltas: 100% (44154/44154), completed with 9484 local objects. From ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/torvalds/linux 4a39ac5b7d62..9852d85ec9d4 master -> linus/master
* [new tag] v5.12-rc1 -> v5.12-rc1 * [new tag] v6.12-rc1 -> v6.12-rc1
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux 6.12-rc1
2024-09-30 13:15 ` Jason A. Donenfeld
@ 2024-09-30 17:22 ` Linus Torvalds
2024-09-30 19:17 ` Jason A. Donenfeld
0 siblings, 1 reply; 9+ messages in thread
From: Linus Torvalds @ 2024-09-30 17:22 UTC (permalink / raw)
To: Jason A. Donenfeld; +Cc: Linux Kernel Mailing List
On Mon, 30 Sept 2024 at 06:15, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Pushed 5.12-rc1 too? Odd.
It's an old tag that was renamed to v5.12-rc1-dontuse when it was
found to have some particularly nasty problems:
https://lore.kernel.org/all/CAHk-=wjnzdLSP3oDxhf9eMTYo7GF-QjaNLBUH1Zk3c4A7X75YA@mail.gmail.com/
For random reasons (read: I had an old repo) it re-materialized under
its old name, and because it was *so* co-incidental in naming (getting
pushed out at the same time as 6.12-rc1), I felt it was too good to
fix up again.
And if somebody goes and randomly starts using v5.12-rc1 (from
February 2021) and hits the swap problem, I can only go "why did you
do that?"
Linus
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Linux 6.12-rc1
2024-09-30 17:22 ` Linus Torvalds
@ 2024-09-30 19:17 ` Jason A. Donenfeld
0 siblings, 0 replies; 9+ messages in thread
From: Jason A. Donenfeld @ 2024-09-30 19:17 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Mon, Sep 30, 2024 at 10:22:28AM -0700, Linus Torvalds wrote:
> On Mon, 30 Sept 2024 at 06:15, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >
> > Pushed 5.12-rc1 too? Odd.
>
> It's an old tag that was renamed to v5.12-rc1-dontuse when it was
> found to have some particularly nasty problems:
>
> https://lore.kernel.org/all/CAHk-=wjnzdLSP3oDxhf9eMTYo7GF-QjaNLBUH1Zk3c4A7X75YA@mail.gmail.com/
>
> For random reasons (read: I had an old repo) it re-materialized under
> its old name, and because it was *so* co-incidental in naming (getting
> pushed out at the same time as 6.12-rc1), I felt it was too good to
> fix up again.
>
> And if somebody goes and randomly starts using v5.12-rc1 (from
> February 2021) and hits the swap problem, I can only go "why did you
> do that?"
Ah, I remember that ordeal. I suppose you've been testing out rc1 on
some different hardware and so old repos are found hither and thither.
Jason
^ permalink raw reply [flat|nested] 9+ messages in thread
* Build regressions/improvements in v6.12-rc1
2024-09-29 22:51 Linux 6.12-rc1 Linus Torvalds
2024-09-30 0:38 ` Guenter Roeck
2024-09-30 13:15 ` Jason A. Donenfeld
@ 2024-09-30 14:53 ` Geert Uytterhoeven
2024-09-30 15:11 ` Geert Uytterhoeven
2024-09-30 17:01 ` Linux 6.12-rc1 Guenter Roeck
3 siblings, 1 reply; 9+ messages in thread
From: Geert Uytterhoeven @ 2024-09-30 14:53 UTC (permalink / raw)
To: linux-kernel
Below is the list of build error/warning regressions/improvements in
v6.12-rc1[1] compared to v6.11[2].
Summarized:
- build errors: +12/-3
- build warnings: +3/-35
Happy fixing! ;-)
Thanks to the linux-next team for providing the build service.
[1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/9852d85ec9d492ebef56dc5f229416c925758edc/ (all 131 configs)
[2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/98f7e32f20d28ec452afb208f9cffc08448a2652/ (all 131 configs)
*** ERRORS ***
12 error regressions:
+ /kisskb/src/fs/bcachefs/backpointers.c: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 504:53
+ /kisskb/src/fs/bcachefs/bcachefs_format.h: error: 'struct bkey' has no member named 'bversion'; did you mean 'version'?: => 332:49, 331:49
+ /kisskb/src/fs/bcachefs/bkey.h: error: 'const struct bkey' has no member named 'bversion': => 578:48
+ /kisskb/src/fs/bcachefs/bkey.h: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 558:27, 557:41, 557:27, 558:41
+ /kisskb/src/fs/bcachefs/bkey.h: error: 'struct bkey' has no member named 'bversion'; did you mean 'version'?: => 557:41, 558:41
+ /kisskb/src/fs/bcachefs/bkey_methods.c: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 292:65
+ /kisskb/src/fs/bcachefs/bkey_methods.h: error: 'const struct bkey' has no member named 'bversion': => 73:31, 73:18
+ /kisskb/src/fs/bcachefs/bkey_methods.h: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 73:33, 73:20, 73:47, 73:34
+ /kisskb/src/fs/bcachefs/bkey_methods.h: error: control reaches end of non-void function [-Werror=return-type]: => 75:1
+ /kisskb/src/fs/bcachefs/disk_accounting.h: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 40:28, 40:42, 39:50, 39:43
+ /kisskb/src/fs/bcachefs/disk_accounting.h: error: 'struct bkey' has no member named 'bversion'; did you mean 'version'?: => 39:26, 40:10, 39:33, 40:24
+ /kisskb/src/include/linux/err.h: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]: => 28:49
3 error improvements:
- /kisskb/src/drivers/md/dm-integrity.c: error: logical not is only applied to the left hand side of comparison [-Werror=logical-not-parentheses]: 4720:45 =>
- /kisskb/src/drivers/media/platform/nxp/imx-pxp.h: error: initializer element is not constant: 582:38 =>
- {standard input}: Error: unknown pseudo-op: `.siz': 1273 =>
*** WARNINGS ***
3 warning regressions:
+ warning: unmet direct dependencies detected for GET_FREE_REGION: => N/A
+ warning: unmet direct dependencies detected for MODVERSIONS: => N/A
+ {standard input}: Warning: macro instruction expanded into multiple instructions: => 285, 339
35 warning improvements:
- /kisskb/src/fs/ext4/readpage.c: warning: the frame size of 1120 bytes is larger than 1024 bytes [-Wframe-larger-than=]: 391:1 =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0x110 (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0x14 (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0x30 (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0x4c (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0x68 (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0x84 (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0xa0 (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0xbc (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0xd8 (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/intel/ice/ice: section mismatch in reference: ice_adv_lnk_speed_maps+0xf4 (section: .data) -> ice_adv_lnk_speed_200000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x14 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x30 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x4c (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x68 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x84 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0xa0 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0xbc (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0xd8 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x14 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x30 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x4c (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x68 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x84 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0xa0 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0xbc (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x14 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x30 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x4c (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x68 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x84 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0xa0 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0xbc (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: lib/test_bitmap: section mismatch in reference: find_next_bit+0x40 (section: .text.unlikely) -> test_print (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: vmlinux: section mismatch in reference: __trace_event_discard_commit+0x184 (section: .text.unlikely) -> initcall_level_names (section: .init.data): N/A =>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Build regressions/improvements in v6.12-rc1
2024-09-30 14:53 ` Build regressions/improvements in v6.12-rc1 Geert Uytterhoeven
@ 2024-09-30 15:11 ` Geert Uytterhoeven
2024-09-30 16:26 ` Herve Codina
0 siblings, 1 reply; 9+ messages in thread
From: Geert Uytterhoeven @ 2024-09-30 15:11 UTC (permalink / raw)
To: linux-kernel
Cc: Kent Overstreet, Herve Codina, Christophe Leroy, linux-bcache,
linuxppc-dev
On Mon, 30 Sep 2024, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v6.12-rc1[1] compared to v6.11[2].
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/9852d85ec9d492ebef56dc5f229416c925758edc/ (all 131 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/98f7e32f20d28ec452afb208f9cffc08448a2652/ (all 131 configs)
>
>
> *** ERRORS ***
>
> 12 error regressions:
> + /kisskb/src/fs/bcachefs/backpointers.c: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 504:53
> + /kisskb/src/fs/bcachefs/bcachefs_format.h: error: 'struct bkey' has no member named 'bversion'; did you mean 'version'?: => 332:49, 331:49
> + /kisskb/src/fs/bcachefs/bkey.h: error: 'const struct bkey' has no member named 'bversion': => 578:48
> + /kisskb/src/fs/bcachefs/bkey.h: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 558:27, 557:41, 557:27, 558:41
> + /kisskb/src/fs/bcachefs/bkey.h: error: 'struct bkey' has no member named 'bversion'; did you mean 'version'?: => 557:41, 558:41
> + /kisskb/src/fs/bcachefs/bkey_methods.c: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 292:65
> + /kisskb/src/fs/bcachefs/bkey_methods.h: error: 'const struct bkey' has no member named 'bversion': => 73:31, 73:18
> + /kisskb/src/fs/bcachefs/bkey_methods.h: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 73:33, 73:20, 73:47, 73:34
> + /kisskb/src/fs/bcachefs/bkey_methods.h: error: control reaches end of non-void function [-Werror=return-type]: => 75:1
> + /kisskb/src/fs/bcachefs/disk_accounting.h: error: 'const struct bkey' has no member named 'bversion'; did you mean 'version'?: => 40:28, 40:42, 39:50, 39:43
> + /kisskb/src/fs/bcachefs/disk_accounting.h: error: 'struct bkey' has no member named 'bversion'; did you mean 'version'?: => 39:26, 40:10, 39:33, 40:24
All big-endian platforms (fix available, even on a public mailing list ;-)
> + /kisskb/src/include/linux/err.h: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]: => 28:49
powerpc-gcc13/ppc64_book3e_allmodconfig
drivers/soc/fsl/qe/qmc.c: In function 'qmc_qe_init_resources':
include/linux/err.h:28:49: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
28 | #define IS_ERR_VALUE(x) unlikely((unsigned long)(void *)(x) >= (unsigned long)-MAX_ERRNO)
| ^
include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
77 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^
drivers/soc/fsl/qe/qmc.c:1764:13: note: in expansion of macro 'IS_ERR_VALUE'
1764 | if (IS_ERR_VALUE(info)) {
| ^~~~~~~~~~~~
IS_ERR_VALUE() is meant for pointers (fix available)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Build regressions/improvements in v6.12-rc1
2024-09-30 15:11 ` Geert Uytterhoeven
@ 2024-09-30 16:26 ` Herve Codina
0 siblings, 0 replies; 9+ messages in thread
From: Herve Codina @ 2024-09-30 16:26 UTC (permalink / raw)
To: Geert Uytterhoeven
Cc: linux-kernel, Kent Overstreet, Christophe Leroy, linux-bcache,
linuxppc-dev
Hi Geert,
On Mon, 30 Sep 2024 17:11:09 +0200 (CEST)
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Mon, 30 Sep 2024, Geert Uytterhoeven wrote:
> > Below is the list of build error/warning regressions/improvements in
> > v6.12-rc1[1] compared to v6.11[2].
...
powerpc-gcc13/ppc64_book3e_allmodconfig
>
> drivers/soc/fsl/qe/qmc.c: In function 'qmc_qe_init_resources':
> include/linux/err.h:28:49: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
> 28 | #define IS_ERR_VALUE(x) unlikely((unsigned long)(void *)(x) >= (unsigned long)-MAX_ERRNO)
> | ^
> include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
> 77 | # define unlikely(x) __builtin_expect(!!(x), 0)
> | ^
> drivers/soc/fsl/qe/qmc.c:1764:13: note: in expansion of macro 'IS_ERR_VALUE'
> 1764 | if (IS_ERR_VALUE(info)) {
> | ^~~~~~~~~~~~
>
> IS_ERR_VALUE() is meant for pointers (fix available)
I saw your patch, tested and acked it.
Thanks for the patch.
Hervé
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux 6.12-rc1
2024-09-29 22:51 Linux 6.12-rc1 Linus Torvalds
` (2 preceding siblings ...)
2024-09-30 14:53 ` Build regressions/improvements in v6.12-rc1 Geert Uytterhoeven
@ 2024-09-30 17:01 ` Guenter Roeck
3 siblings, 0 replies; 9+ messages in thread
From: Guenter Roeck @ 2024-09-30 17:01 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Sun, Sep 29, 2024 at 03:51:43PM -0700, Linus Torvalds wrote:
> So two weeks have passed, and rc1 is out - the merge window is closed.
>
> Despite conference travel (both for me and several maintainers),
> things seemed to go mostly fairly normally. There's a couple of
> notable new features in here: For one thing, PREEMPT_RT is now
> mainlined and enabled as a config option (you do need to enable
> "EXPERT" to get the question). For another, sched_ext also got merged.
>
> That said, the bulk is - as always - all the plain old regular
> updates, and that obviously means drivers dominate. We've got about
> 55% of the patch being drivers (and another 5% if you count the dts
> files). Add in 5% doc updates, and 10% tooling (mostly perf and
> selftests).
>
> That leaves about a quarter of the overall changes as core kernel
> code, split between arch updates, filesystems (yes, bcachefs, but also
> btrfs, smb sever and client, netfs updates, xfs and finally core VFS
> updates mostly in the form of 'struct fd' re-organisational cleanups).
> And MM, core networking, Rust, security layer updates etc.
>
> A little bit of everything, in other words. And nothing really looks
> all that strange. As always, the summary below is just the log of my
> merges, there's too much to list individually (some stats: 11k+
> regular commits, 850+ merges, 1700+ different authors).
>
> Let's get the testing and calming down period started, ok?
>
Build results:
total: 158 pass: 145 fail: 13
Failed builds:
m68k:defconfig
m68k:allmodconfig
m68k:sun3_defconfig
mips:allmodconfig
openrisc:allmodconfig
parisc:allmodconfig
powerpc:allmodconfig
powerpc:ppc32_allmodconfig
s390:defconfig
s390:allmodconfig
s390:debug_defconfig
sparc64:allmodconfig
xtensa:allmodconfig
Qemu test results:
total: 555 pass: 522 fail: 33
Failed tests:
<all arm64be>
<all m68k:q800>
<all s390>
Unit test results:
pass: 430107 fail: 1
Failed tests:
arm:orangepi-pc:vcap_api_iterator_init_test
arm:orangepi-pc:VCAP_API_Encoding_Testsuite
As far as I can see, all build and qemu test failures are due to the
bcachefs patch that broke big endian builds.
I have not analyzed the vcap unit test failure.
I had to disable a number of kunit tests. Also, there are some new
backtraces. See below for details.
Guenter
---
On mips64, qemu malta machine:
rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
rcu: (detected by 0, t=2603 jiffies, g=1077, q=7017 ncpus=1)
rcu: All QSes seen, last rcu_sched kthread activity 2603 (4294942579-4294939976), jiffies_till_next_fqs=1, root ->qsmask 0x0
rcu: rcu_sched kthread starved for 2603 jiffies! g1077 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0
rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_sched state:R running task stack:0 pid:14 tgid:14 ppid:2 flags:0x00100000
Stack : 900000000231c498 90000000022f4720 ffffffff813f02f0 90000000032c30a0
0000000000000000 0000fb5b00000000 ffffffff80f1ea90 0000000000000000
0000000200000000 00296d890e82bf6f 90000000032c28c0 ffffffff813f0000
ffffffff813e0000 ffffffff80f20000 0000000000000001 ffffffff81413c98
ffffffff81410000 0000000000000001 ffffffff81413740 ffffffff80f09158
ffffffff81410000 00000000ffff9549 ffffffff813e0000 ffffffff80f13128
0000000000000122 0000000000000000 00000000ffff9549 ffffffff80206c28
0280000000000000 ffffffff8207bce8 0000000000000000 0000000000000000
ffffffff81239438 0000000000000000 90000000032c28c0 00296d890e82bf6f
ffffffff81522748 0000000000000000 ffffffff813e0000 ffffffff813df318
...
Call Trace:
[<ffffffff80f08788>] __schedule+0x538/0xeb8
[<ffffffff80f09158>] schedule+0x50/0x1e0
[<ffffffff80f13128>] schedule_timeout+0xc8/0x170
[<ffffffff801e8f50>] rcu_gp_fqs_loop+0x6a0/0xa00
[<ffffffff801ee768>] rcu_gp_kthread+0x1c8/0x378
[<ffffffff8016e3b4>] kthread+0x134/0x160
[<ffffffff80103328>] ret_from_kernel_thread+0x14/0x1c
rcu: Stack dump where RCU GP kthread last ran:
Seen once while running rbtree-default test. Not analyzed.
---
powerpc, with qemu mpc8544ds machine and SMP configurations:
LSM: initializing lsm=lockdown,capability,landlock,yama,loadpin,safesetid,ipe
------------[ cut here ]------------
WARNING: CPU: 0 PID: 0 at kernel/smp.c:807 smp_call_function_many_cond+0x4f4/0x9d0
Modules linked in:
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.0-rc1 #1
Hardware name: MPC8544DS e500v2 0x80210030 MPC8544 DS
NIP: c017c964 LR: c017ce8c CTR: 00000000
REGS: c267dd40 TRAP: 0700 Not tainted (6.12.0-rc1)
MSR: 00021000 <CE,ME> CR: 24004288 XER: 20000000
GPR00: c00225a4 c267de30 c254c5c0 c26924c4 00000000 00000000 00000001 c2690000
GPR08: 00000000 00000003 c2690000 00000000 84004288 020a6fb8 00000000 00000000
GPR16: 00000000 00000000 00000000 00000000 c0000000 00000001 00000000 cfffd0c0
GPR24: c017ce8c c26924c4 c0022544 00000000 00000000 00029000 4bffd2d8 00000000
NIP [c017c964] smp_call_function_many_cond+0x4f4/0x9d0
LR [c017ce8c] smp_call_function+0x3c/0x58
Call Trace:
[c267de90] [84000282] 0x84000282
[c267dea0] [c00225a4] flush_tlb_kernel_range+0x2c/0x50
[c267deb0] [c0023bb4] patch_mem.constprop.0+0x108/0x1b0
[c267ded0] [c00188ac] arch_static_call_transform+0x10c/0x150
[c267def0] [c2035fa8] security_add_hooks+0x138/0x24c
[c267df20] [c2034dac] capability_init+0x24/0x38
[c267df30] [c20352bc] initialize_lsm+0x48/0x90
[c267df50] [c2035b9c] security_init+0x2e0/0x5b4
[c267dfa0] [c2001154] start_kernel+0x5d4/0x81c
[c267dff0] [c0000478] set_ivor+0x150/0x18c
Code: 91220000 81620004 3d20c209 39293478 556b103a 7c84582e 7c89202e 81220000 2c040000 3929ffff 91220000 40a2fbdc <0fe00000> 4bfffbd4 80e20000 2c070000
irq event stamp: 1198
hardirqs last enabled at (1197): [<c11fa128>] _raw_spin_unlock_irqrestore+0x70/0xa8
hardirqs last disabled at (1198): [<c0023bf4>] patch_mem.constprop.0+0x148/0x1b0
softirqs last enabled at (10): [<c0064c88>] handle_softirqs+0x344/0x500
softirqs last disabled at (3): [<c0006fd8>] do_softirq_own_stack+0x34/0x4c
---[ end trace 0000000000000000 ]---
landlock: Up and running.
I tried to bisect, but did not get anywhere due to build failures and
crashes during the bisect.
---
Overall kunit status in my test bed
- Newly enabled configurations and tests
Either those are new tests, or a previously observed problem with test
has been fixed.
CONFIG_SECURITY_APPARMOR_KUNIT_TEST
CONFIG_SECURITY_IPE
CONFIG_SECURITY_IPE_KUNIT_TEST
CONFIG_PM_QOS_KUNIT_TEST
CONFIG_EXT4_KUNIT_TESTS
CONFIG_IIO_GTS_KUNIT_TEST
- New, not enabled
CONFIG_MCTP_SERIAL_TEST
Crashes in mctp_i2c_get_adapter().
- Partially enabled
CONFIG_DAMON_KUNIT_TEST
CONFIG_DAMON_VADDR_KUNIT_TEST
CONFIG_DAMON_DBGFS_KUNIT_TEST
Fail with 32-bit configurations and only enabled for 64-bit builds.
CONFIG_OF_KUNIT_TEST
CONFIG_OF_OVERLAY_KUNIT_TEST (new)
CONFIG_CLK_FIXED_RATE_KUNIT_TEST (new)
CONFIG_CLK_KUNIT_TEST (previously enabled)
Fail on arm64 when booting through EFI and therefore disabled for
arm64; still enabled otherwise if COMMON_CLK is enabled.
- Previously enabled, now disabled
CONFIG_KUNIT_TEST
Now triggers intentional backtraces.
CONFIG_TEST_IOV_ITER
Still enabled everywhere except openrisc, where it crashes.
Crash is most likely due to an architecture specific problem.
CONFIG_SLUB_KUNIT_TEST
Now triggers intentional backtraces, and fails completely when builtin
and run at boot time because it now needs RCU, but RCU is not yet
initialized when unit tests are run during boot.
Patches to fix the problems have been submitted.
^ permalink raw reply [flat|nested] 9+ messages in thread