1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.RELEAS

  • Uploading linux (6.12.24-1)

    From Salvatore Bonaccorso@21:1/5 to All on Mon Apr 21 14:10:02 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Hi

    Following the tradition to keep up with upstream stable releases and
    aiming to have a trixie close to upstream, I would like to upload
    linux version 6.12.24-1 to unstable.

    6.12.22-1 has moved already to testing so far.

    Debian Boot, Release team how is the timing with respect potential d-i
    work?

    The new version imports stable series versions up to 6.12.24. Those
    are relatively big given they were the first after the 6.15 merge
    window. I would expect we might encounter some (yet undetected)
    problems, which will be soon then addressed in followup stable series
    as well. Several (known) CVEs are covered in those releases:
    CVE-2023-53034, CVE-2025-22024, CVE-2025-22025, CVE-2025-22027,
    CVE-2025-22028, CVE-2025-22029, CVE-2025-22030, CVE-2025-22032,
    CVE-2025-22033, CVE-2025-22034, CVE-2025-22035, CVE-2025-22036,
    CVE-2025-22037, CVE-2025-22038, CVE-2025-22039, CVE-2025-22040,
    CVE-2025-22041, CVE-2025-22042, CVE-2025-22043, CVE-2025-22044,
    CVE-2025-22045, CVE-2025-22046, CVE-2025-22047, CVE-2025-22048,
    CVE-2025-22049, CVE-2025-22050, CVE-2025-22053, CVE-2025-22054,
    CVE-2025-22055, CVE-2025-22056, CVE-2025-22057, CVE-2025-22058,
    CVE-2025-22059, CVE-2025-22060, CVE-2025-22062, CVE-2025-22063,
    CVE-2025-22064, CVE-2025-22065, CVE-2025-22066, CVE-2025-22067,
    CVE-2025-22068, CVE-2025-22070, CVE-2025-22071, CVE-2025-22072,
    CVE-2025-22073, CVE-2025-22074, CVE-2025-22075, CVE-2025-22076,
    CVE-2025-22077, CVE-2025-22078, CVE-2025-22079, CVE-2025-22080,
    CVE-2025-22081, CVE-2025-22082, CVE-2025-22083, CVE-2025-22084,
    CVE-2025-22085, CVE-2025-22086, CVE-2025-22087, CVE-2025-22088,
    CVE-2025-22089, CVE-2025-22090, CVE-2025-22091, CVE-2025-22093,
    CVE-2025-22095, CVE-2025-22097, CVE-2025-23134, CVE-2025-23136,
    CVE-2025-23138, CVE-2025-37785, CVE-2025-37893, CVE-2025-38049,
    CVE-2025-38152, CVE-2025-38240, CVE-2025-38479, CVE-2025-38575,
    CVE-2025-38637, CVE-2025-39688, CVE-2025-39728, CVE-2025-39735,
    CVE-2025-39778, CVE-2025-39989 and CVE-2025-40114 (although I guess
    it's bit moot to list the CVEs known for those stable releases, we
    have plenty on each round anyway ;-)).

    Some packaging changes are included, so far they are:

    * [arm64,powerpc,ppc64,ppc64el,riscv64,s390x] Enable KALLSYMS_ALL on
    all architectures where DEBUG_INFO_BTF is on (Closes: #1100634)
    * hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key

    (note the later one is a LPE, "longstanding" already, but see upstream discussion about HFS/HFS+, we aimed initially to have support for
    those filesystem dropped, but at this point it is not possible).

    Kernel team, we have a couple of merge requests which we aim to have
    backported as well to trixie, I think it would be good that we can
    include hose as well, meaning we have to first merge them into
    debian/latest for experimental:

    1464 d/rules.real: Export CROSS_COMPILE_COMPAT, CROSS32_COMPILE variables
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1464
    1466 Fix various lintian errors and warnings
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1466
    1467 linux-kbuild: Fix cross-build regression (needs reveiw)
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1467

    where the first and last are rgressions we need to handle.

    The following are merged already in debian/latest

    1295 [arm64] Fixes for MediaTek Chromebooks
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1295
    1302 udeb: Add onboard_usb_dev to usb-modules
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1302
    1463 drivers/hwmon/pmbus: Enable PMBUS and SENSORS_PMBUS as modules
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1463

    Those add HW support.

    Comments? Concerns about the timing? Go ahead?

    Regards,
    Salvatore

    -----BEGIN PGP SIGNATURE-----

    iQKTBAABCgB9FiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmgGM8NfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQACgkQBUy48xND z0SW6A//QAXacx8RSXuAoFTz6pjmYwSIP/Ecd2oVO2vLehnUuAnL+CBKxzFgMkKM aUcPI8lHkn8TJ6Mjts/1ukL4ao0nbtnYe6w3V13A6lqFNsRFCG8kpkHKotdI/bov GhpOsv0miFbqH6NScZyb2DbXQ7mOwEPaRmlIjQ2l2FZJbqnivQedebD5VJfQaERg aQaI80UdNeK/hgQVD7EPI3mbqf7Kd8r/KWFMGegT7BUEREt/i22FhfN1hAMYG4Zv VTFagOr32CiA+qUhXORNEB34d9ynsa3AZI5xjP0qkzgQ3Y791XqHCD5uPZTyO8yD h0HD0nbHbsTGUzqBz8Laml/lOrOyjIYJyMSTjgxgH/icFmOUV6mJwtS00jO2zr1/ j5wF2rGFGMSVt4k/1IcWUwG1b1FMMN2BQ9wvy2a9cR7uKVEv8Q/YetMQpr6cnW6T okdW2n8wR0jTliANgKf5tbn3wml19vn0Y8U1QUA4GbBg19kDrvhZ0S9ChIQbSJew NXy58KvfOqB4Sz1gv/pyL6dWouXOLBP1BIFT6D4g8xZ8oD+cF9Zr28N05/cBobCC 306uEwI1e94pbm91q2mPTpLQYtXdzR2qr4bxZ2G2ptnhkKaV/mn0YsIntITBXvca G5BZDkEfEXJJN5+SO8PyM2AkkJ/e3IwtoS89ZjG18+/gKGyDwy8=
    =SQ2l
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cyril Brulebois@21:1/5 to All on Mon Apr 21 17:20:01 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Hi,

    Salvatore Bonaccorso <[email protected]> (2025-04-21):
    Debian Boot, Release team how is the timing with respect potential d-i
    work?

    That's fine for d-i.


    Cheers,
    --
    Cyril Brulebois ([email protected]) <https://debamax.com/>
    D-I release manager -- Release team member -- Freelance Consultant

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmgGYFgACgkQ/5FK8MKz VSDNUBAArASOZUITjYECJPRuL+silbHLTe8IBK4Lm1FpGus8KF8Eeny0Sc+0ETHM rNel64T2IHiINcZutxhCFxGbFZclUZBhAMC8ECoP6hfWovldwpkLOdOAsr2cJ2m9 FgNFtpNa74+LDExyKL3ErfoMOMRd/arDoGhPcO7OBxR5soDp4nKkRU3DbzdCPhwg 6lE99PQiLnfL0vf2fQH/ZK1QCxJjHHZjwqZ+7qp7TbBdjXNw6jscdoxrS1LDNeSW 0BLFTGNisWVz9yDJ/f6JorkC6AuUII7y+SpX7PJrcsb5Tf0A4IbZofk8AVmAb2HS gaAX1tjJEPNZgFGiOCs2Frp4YG3cmGuH3F2i53gmaWr/nHcK8lFlQ7xAN7KrI0iD rnG5o9iDbLlDD/IZPI+mpcdR8K/QV7M8aLzKyXejrk/W76+QVqwDET/kZjD/K4+i EdPptr9QEC8OQPJita1257Moo0/jfbTlBB7AcYgb1WbeRQMpwzK5YneHoaT5hR6I wZgiuQ4IE43WgWeSzC3AlYgeZziOMjf88klHv1dxzGtYrp+17+G1CvFmP5uUObll IftzzIY0+O5LSxdd0sCfv8paV6scYaCkyFPzcoFTEUw50diiScb+vzA0cn4PJRO9 zM8g9rklCC1GqVyKvsn+Il6MlnRGYgGwCMWcVM4+zZL/SBzmA0I=
    =ppoQ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *
  • From John Paul Adrian Glaubitz@21:1/5 to Salvatore Bonaccorso on Mon Apr 21 18:50:01 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Hi Salvatore,

    On Mon, 2025-04-21 at 14:02 +0200, Salvatore Bonaccorso wrote:
    * [arm64,powerpc,ppc64,ppc64el,riscv64,s390x] Enable KALLSYMS_ALL on
    all architectures where DEBUG_INFO_BTF is on (Closes: #1100634)
    * hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key

    (note the later one is a LPE, "longstanding" already, but see upstream discussion about HFS/HFS+, we aimed initially to have support for
    those filesystem dropped, but at this point it is not possible).

    I'm adopting the HFS/HFS+ driver now together with a developer from IBM
    and I think it would be a good idea to get these patches merged upstream
    as soon as possible.

    Adrian

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer
    `. `' Physicist
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Salvatore Bonaccorso@21:1/5 to John Paul Adrian Glaubitz on Mon Apr 21 21:30:01 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Hi Adrian,

    On Mon, Apr 21, 2025 at 06:45:49PM +0200, John Paul Adrian Glaubitz wrote:
    Hi Salvatore,

    On Mon, 2025-04-21 at 14:02 +0200, Salvatore Bonaccorso wrote:
    * [arm64,powerpc,ppc64,ppc64el,riscv64,s390x] Enable KALLSYMS_ALL on
    all architectures where DEBUG_INFO_BTF is on (Closes: #1100634)
    * hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key

    (note the later one is a LPE, "longstanding" already, but see upstream discussion about HFS/HFS+, we aimed initially to have support for
    those filesystem dropped, but at this point it is not possible).

    I'm adopting the HFS/HFS+ driver now together with a developer from IBM
    and I think it would be a good idea to get these patches merged upstream
    as soon as possible.

    Thanks for that.

    FWIW, the specific one above has landed in mainline and should
    hopefully made his way as well to the stable series. But thee is more.

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Salvatore Bonaccorso@21:1/5 to Salvatore Bonaccorso on Wed Apr 23 22:00:01 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Hi all,

    On Mon, Apr 21, 2025 at 02:02:19PM +0200, Salvatore Bonaccorso wrote:
    Hi

    Following the tradition to keep up with upstream stable releases and
    aiming to have a trixie close to upstream, I would like to upload
    linux version 6.12.24-1 to unstable.

    6.12.22-1 has moved already to testing so far.

    Debian Boot, Release team how is the timing with respect potential d-i
    work?

    The new version imports stable series versions up to 6.12.24. Those
    are relatively big given they were the first after the 6.15 merge
    window. I would expect we might encounter some (yet undetected)
    problems, which will be soon then addressed in followup stable series
    as well. Several (known) CVEs are covered in those releases:
    CVE-2023-53034, CVE-2025-22024, CVE-2025-22025, CVE-2025-22027, CVE-2025-22028, CVE-2025-22029, CVE-2025-22030, CVE-2025-22032, CVE-2025-22033, CVE-2025-22034, CVE-2025-22035, CVE-2025-22036, CVE-2025-22037, CVE-2025-22038, CVE-2025-22039, CVE-2025-22040, CVE-2025-22041, CVE-2025-22042, CVE-2025-22043, CVE-2025-22044, CVE-2025-22045, CVE-2025-22046, CVE-2025-22047, CVE-2025-22048, CVE-2025-22049, CVE-2025-22050, CVE-2025-22053, CVE-2025-22054, CVE-2025-22055, CVE-2025-22056, CVE-2025-22057, CVE-2025-22058, CVE-2025-22059, CVE-2025-22060, CVE-2025-22062, CVE-2025-22063, CVE-2025-22064, CVE-2025-22065, CVE-2025-22066, CVE-2025-22067, CVE-2025-22068, CVE-2025-22070, CVE-2025-22071, CVE-2025-22072, CVE-2025-22073, CVE-2025-22074, CVE-2025-22075, CVE-2025-22076, CVE-2025-22077, CVE-2025-22078, CVE-2025-22079, CVE-2025-22080, CVE-2025-22081, CVE-2025-22082, CVE-2025-22083, CVE-2025-22084, CVE-2025-22085, CVE-2025-22086, CVE-2025-22087, CVE-2025-22088, CVE-2025-22089, CVE-2025-22090, CVE-2025-22091, CVE-2025-22093, CVE-2025-22095, CVE-2025-22097, CVE-2025-23134, CVE-2025-23136, CVE-2025-23138, CVE-2025-37785, CVE-2025-37893, CVE-2025-38049, CVE-2025-38152, CVE-2025-38240, CVE-2025-38479, CVE-2025-38575, CVE-2025-38637, CVE-2025-39688, CVE-2025-39728, CVE-2025-39735, CVE-2025-39778, CVE-2025-39989 and CVE-2025-40114 (although I guess
    it's bit moot to list the CVEs known for those stable releases, we
    have plenty on each round anyway ;-)).

    Some packaging changes are included, so far they are:

    * [arm64,powerpc,ppc64,ppc64el,riscv64,s390x] Enable KALLSYMS_ALL on
    all architectures where DEBUG_INFO_BTF is on (Closes: #1100634)
    * hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key

    (note the later one is a LPE, "longstanding" already, but see upstream discussion about HFS/HFS+, we aimed initially to have support for
    those filesystem dropped, but at this point it is not possible).

    Kernel team, we have a couple of merge requests which we aim to have backported as well to trixie, I think it would be good that we can
    include hose as well, meaning we have to first merge them into
    debian/latest for experimental:

    1464 d/rules.real: Export CROSS_COMPILE_COMPAT, CROSS32_COMPILE variables
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1464
    1466 Fix various lintian errors and warnings
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1466
    1467 linux-kbuild: Fix cross-build regression (needs reveiw)
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1467

    where the first and last are rgressions we need to handle.

    The following are merged already in debian/latest

    1295 [arm64] Fixes for MediaTek Chromebooks
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1295
    1302 udeb: Add onboard_usb_dev to usb-modules
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1302
    1463 drivers/hwmon/pmbus: Enable PMBUS and SENSORS_PMBUS as modules
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1463

    Those add HW support.

    Comments? Concerns about the timing? Go ahead?

    FTR, I'm delaying this upload to get 6.12.25 in as well which is
    currently reviewed *and* as discussed briefly in todays kernel team
    meeting, wait until we have he pending merge requests targeting trixie
    in in experimental first with a 6.14.y upload ideally, just to have
    some additional exposure.

    I hope this still does not clash with d-i preparations or release-team timelines. Let me please know otherwise.

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cyril Brulebois@21:1/5 to All on Thu Apr 24 00:10:02 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Still green for d-i.

    Le 23 avr. 2025 à 21:58, Salvatore Bonaccorso <[email protected]> a écrit :

    Hi all,

    On Mon, Apr 21, 2025 at 02:02:19PM +0200, Salvatore Bonaccorso wrote:
    Hi

    Following the tradition to keep up with upstream stable releases and
    aiming to have a trixie close to upstream, I would like to upload
    linux version 6.12.24-1 to unstable.

    6.12.22-1 has moved already to testing so far.

    Debian Boot, Release team how is the timing with respect potential d-i
    work?

    The new version imports stable series versions up to 6.12.24. Those
    are relatively big given they were the first after the 6.15 merge
    window. I would expect we might encounter some (yet undetected)
    problems, which will be soon then addressed in followup stable series
    as well. Several (known) CVEs are covered in those releases:
    CVE-2023-53034, CVE-2025-22024, CVE-2025-22025, CVE-2025-22027,
    CVE-2025-22028, CVE-2025-22029, CVE-2025-22030, CVE-2025-22032,
    CVE-2025-22033, CVE-2025-22034, CVE-2025-22035, CVE-2025-22036,
    CVE-2025-22037, CVE-2025-22038, CVE-2025-22039, CVE-2025-22040,
    CVE-2025-22041, CVE-2025-22042, CVE-2025-22043, CVE-2025-22044,
    CVE-2025-22045, CVE-2025-22046, CVE-2025-22047, CVE-2025-22048,
    CVE-2025-22049, CVE-2025-22050, CVE-2025-22053, CVE-2025-22054,
    CVE-2025-22055, CVE-2025-22056, CVE-2025-22057, CVE-2025-22058,
    CVE-2025-22059, CVE-2025-22060, CVE-2025-22062, CVE-2025-22063,
    CVE-2025-22064, CVE-2025-22065, CVE-2025-22066, CVE-2025-22067,
    CVE-2025-22068, CVE-2025-22070, CVE-2025-22071, CVE-2025-22072,
    CVE-2025-22073, CVE-2025-22074, CVE-2025-22075, CVE-2025-22076,
    CVE-2025-22077, CVE-2025-22078, CVE-2025-22079, CVE-2025-22080,
    CVE-2025-22081, CVE-2025-22082, CVE-2025-22083, CVE-2025-22084,
    CVE-2025-22085, CVE-2025-22086, CVE-2025-22087, CVE-2025-22088,
    CVE-2025-22089, CVE-2025-22090, CVE-2025-22091, CVE-2025-22093,
    CVE-2025-22095, CVE-2025-22097, CVE-2025-23134, CVE-2025-23136,
    CVE-2025-23138, CVE-2025-37785, CVE-2025-37893, CVE-2025-38049,
    CVE-2025-38152, CVE-2025-38240, CVE-2025-38479, CVE-2025-38575,
    CVE-2025-38637, CVE-2025-39688, CVE-2025-39728, CVE-2025-39735,
    CVE-2025-39778, CVE-2025-39989 and CVE-2025-40114 (although I guess
    it's bit moot to list the CVEs known for those stable releases, we
    have plenty on each round anyway ;-)).

    Some packaging changes are included, so far they are:

    * [arm64,powerpc,ppc64,ppc64el,riscv64,s390x] Enable KALLSYMS_ALL on
    all architectures where DEBUG_INFO_BTF is on (Closes: #1100634)
    * hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key

    (note the later one is a LPE, "longstanding" already, but see upstream
    discussion about HFS/HFS+, we aimed initially to have support for
    those filesystem dropped, but at this point it is not possible).

    Kernel team, we have a couple of merge requests which we aim to have
    backported as well to trixie, I think it would be good that we can
    include hose as well, meaning we have to first merge them into
    debian/latest for experimental:

    1464 d/rules.real: Export CROSS_COMPILE_COMPAT, CROSS32_COMPILE variables
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1464
    1466 Fix various lintian errors and warnings
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1466
    1467 linux-kbuild: Fix cross-build regression (needs reveiw)
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1467

    where the first and last are rgressions we need to handle.

    The following are merged already in debian/latest

    1295 [arm64] Fixes for MediaTek Chromebooks
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1295
    1302 udeb: Add onboard_usb_dev to usb-modules
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1302
    1463 drivers/hwmon/pmbus: Enable PMBUS and SENSORS_PMBUS as modules
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1463

    Those add HW support.

    Comments? Concerns about the timing? Go ahead?

    FTR, I'm delaying this upload to get 6.12.25 in as well which is
    currently reviewed *and* as discussed briefly in todays kernel team
    meeting, wait until we have he pending merge requests targeting trixie
    in in experimental first with a 6.14.y upload ideally, just to have
    some additional exposure.

    I hope this still does not clash with d-i preparations or release-team timelines. Let me please know otherwise.

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)