Tags

v6.1.106

This is the 6.1.106 stable release

v5.15.165

This is the 5.15.165 stable release

v5.10.224

This is the 5.10.224 stable release

v5.4.282

This is the 5.4.282 stable release

v4.19.320

This is the 4.19.320 stable release

v6.11-rc4

Linux 6.11-rc4

asahi-6.10.5-1

Tagging asahi-6.10.5-1

- macsmc-power Sequoia fixes
- rebase onto v6.10.5

rust-fixes-6.11

Rust fixes for v6.11

 - Fix '-Os' Rust 1.80.0+ builds adding more intrinsics (also tweaked
   in upstream Rust for the upcoming 1.82.0).

 - Fix support for the latest version of rust-analyzer due to a change
   on rust-analyzer config file semantics (considered a fix since most
   developers use the latest version of the tool, which is the only one
   actually supported by upstream). I am discussing stability of the
   config file with upstream -- they may be able to start versioning it.

 - Fix GCC 14 builds due to '-fmin-function-alignment' not skipped for
   libclang (bindgen).

 - A couple Kconfig fixes around '{RUSTC,BINDGEN}_VERSION_TEXT' to
   suppress error messages in a foreign architecture chroot and to use a
   proper default format.

 - Clean 'rust-analyzer' target warning due to missing recursive make
   invocation mark.

 - Clean Clippy warning due to missing indentation in docs.

 - Clean LLVM 19 build warning due to removed 3dnow feature upstream.

v6.10.5

This is the 6.10.5 stable release

v6.6.46

This is the 6.6.46 stable release

v6.1.105

This is the 6.1.105 stable release

v6.11-rc3

Linux 6.11-rc3

x86-urgent-2024-08-11

A set of x86 fixes:

  - Fix 32-bit PTI for real. pti_clone_entry_text() is called twice, once
    before initcalls so that initcalls can use the user-mode helper and
    then again after text is set read only. Setting read only on 32-bit
    might break up the PMD mapping, which makes the second invocation of
    pti_clone_entry_text() find the mappings out of sync and failing.

    Allow the second call to split the existing PMDs in the user mapping
    and synchronize with the kernel mapping.

  - Don't make acpi_mp_wake_mailbox not read only after init as the mail
    box must be writable in the case that CPU hotplug operations happen
    after boot. Otherwise the attempt to start a CPU crashes with a write
    to read only memory.

  - Add a missing sanity check in mtrr_save_state() to ensure that the
    fixed MTRR MSRs are supported.

    Otherwise mtrr_save_state() ends up in a #GP, which is fixed up, but
    the WARN_ON() can bring systems down when panic on warn is set.

timers-urgent-2024-08-11

Updates for time keeping:

  - Fix a couple of issues in the NTP code where user supplied values are
    neither sanity checked nor clamped to the operating range. This results
    in integer overflows and eventualy NTP getting out of sync.

    According to the history the sanity checks had been removed in favor of
    clamping the values, but the clamping never worked correctly under all
    circumstances. The NTP people asked to not bring the sanity checks back
    as it might break existing applications.

    Make the clamping work correctly and add it where it's missing

  - If adjtimex() sets the clock it has to trigger the hrtimer subsystem so
    it can adjust and if the clock was set into the future expire timers if
    needed. The caller should provide a bitmask to tell hrtimers which
    clocks have been adjusted. adjtimex() uses not the proper constant and
    uses CLOCK_REALTIME instead, which is 0. So hrtimers adjusts only the
    clocks, but does not check for expired timers, which might make them
    expire really late. Use the proper bitmask constant instead.

irq-urgent-2024-08-11

Three small fixes for interrupt core and drivers:

    - The interrupt core fails to honor caller supplied affinity hints for
      non-managed interrupts and uses the system default affinity on
      startup instead. Set the missing flag in the descriptor to tell the
      core to use the provided affinity.

    - Fix a shift out of bounds error in the Xilinx driver

    - Handle switching to level trigger correctly in the RISCV APLIC
      driver. It failed to retrigger the interrupt which causes it to
      become stale.

v6.10.4

This is the 6.10.4 stable release

v6.6.45

This is the 6.6.45 stable release

v6.1.104

This is the 6.1.104 stable release

irq-domain-24-08-09

irqdomain changes required for regmap to apply depending patches

6.6.44-118