mbox series

[bug#70335,0/4] linux-libre kernel updates (2024-04-11)

Message ID cover.1712825806.git.w@wmeyer.eu
Headers show
Series linux-libre kernel updates (2024-04-11) | expand

Message

Wilko Meyer April 11, 2024, 8:59 a.m. UTC 
Hi Leo,

There's been another round of updates again affecting all currently supported
6.x series kernels as well as 5.15.x.

Deblob scripts didn't change this time:

1kqwcm8baq3zx1z8jrgnvm9yps3y9jbf4pv1pbqqprpdscgl9089 0j9pj370zismhzw18iyx3lwcby3l3160xgpmh5xa8i8cr38r2z5h 6.8.5
1qm8f3fq4yx59f7b6yky5ryyf229ypxnry922sr8cy0s7mp62cmv 17hq5pirvxaq1yscb204950xlakrd4r4mknjqayh1rzj4rzngzyq 6.6.26
1sf80f2i4vf888xjcn84ymn4w5ynn30ib9033zwmv7f09yvfhapy 1kp8zl97x1hsmvmdwaq8s8gndfmf8chvlhsw216f86ishi2prws3 6.1.85
18ac30kxg2mf2f6gk3p935hzhz2qs110jy4xwk21kblnnkskbxj8 121shkzgixmywa19xx5f2yxg1primarpg4bxin3jyw0214xbfh2n 5.15.154

Wilko Meyer (4):
  gnu: linux-libre 6.8: Update to 6.8.5.
  gnu: linux-libre 6.6: Update to 6.6.26.
  gnu: linux-libre 6.1: Update to 6.1.85.
  gnu: linux-libre 5.15: Update to 5.15.154.

 gnu/packages/linux.scm | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)


base-commit: c2985764871597a99fde8c48b8958cecdd4fb0f5

Comments

Wilko Meyer April 11, 2024, 9:13 a.m. UTC | #1 
It seems that there's a known issue[0] with at least the 6.8.5 and
6.6.26 releases of this round, preventing system boot if
CONFIG_GCC_PLUGIN_STACKLEAK is set, as we have enabled it for all 6.x.x
kernels:

λ rg -c 'CONFIG_GCC_PLUGIN_STACKLEAK=y' linux-libre/6.*
linux-libre/6.8-x86_64.conf:1
linux-libre/6.8-i686.conf:1
linux-libre/6.8-arm64.conf:1
linux-libre/6.7-x86_64.conf:1
linux-libre/6.7-i686.conf:1
linux-libre/6.7-arm64.conf:1
linux-libre/6.6-x86_64.conf:1
linux-libre/6.6-i686.conf:1
linux-libre/6.6-arm64.conf:1
linux-libre/6.1-x86_64.conf:1
linux-libre/6.1-i686.conf:1
linux-libre/6.1-arm64.conf:1

we seem to have three options:

- applying
  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e7d24c0aa8e678f41457d1304e2091cac6fd1a2e
  as suggested on the corresponding LKML thread[1].
- holding back this round for 6.8.x and 6.6.x. until next weeks round.
- applying it and hope it won't cause too much breakage

3. seems to be the worst option with the bug report in mind, 2. would be
the option with the least overhead. 1. would have some overhead but
seems to fix the situation so this round would be usable. WDYT?

[0]: https://fosstodon.org/@kernellogger/112251747670970164
[1]: https://lore.kernel.org/all/CAMj1kXHgvv0FYZXsFm8KisXuR6t47-nXtgOs0Gyva4MJEJ_4Ow@mail.gmail.com/#t
Leo Famulari April 11, 2024, 7:17 p.m. UTC | #2 
On Thu, Apr 11, 2024 at 10:59:12AM +0200, Wilko Meyer wrote:
> Hi Leo,
> 
> There's been another round of updates again affecting all currently supported
> 6.x series kernels as well as 5.15.x.
> 
> Deblob scripts didn't change this time:

Thanks! Pushed to 'kernel-updates':

https://ci.guix.gnu.org/eval/1241100
Leo Famulari April 13, 2024, 2:15 a.m. UTC | #3 
On Thu, Apr 11, 2024 at 10:59:12AM +0200, Wilko Meyer wrote:
> Wilko Meyer (4):
>   gnu: linux-libre 6.8: Update to 6.8.5.
>   gnu: linux-libre 6.6: Update to 6.6.26.
>   gnu: linux-libre 6.1: Update to 6.1.85.
>   gnu: linux-libre 5.15: Update to 5.15.154.

Pushed as 15a523ea213065c275e4852673cbb27c72c0ad87

Thanks again!