Peter Michael Green [Sat, 24 Jan 2026 11:28:04 +0000 (11:28 +0000)]
fix buildid patch.
Peter Michael Green [Sat, 24 Jan 2026 06:52:53 +0000 (06:52 +0000)]
update quilt patch.
Peter Michael Green [Sat, 24 Jan 2026 06:36:10 +0000 (06:36 +0000)]
Manual merge of version 6.12.41-1+rpi1 and 6.17.13-1 to produce 6.17.13-1+rpi1
Salvatore Bonaccorso [Sat, 20 Dec 2025 09:15:48 +0000 (10:15 +0100)]
Merge linux (6.17.13-1) import into refs/heads/workingbranch
Ben Hutchings [Sun, 15 Jun 2025 21:35:52 +0000 (23:35 +0200)]
tools/hv: Make the sample hv_get_dhcp_info script more useful
Origin: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit?id=
29c75ddc2d1952528a1195b6ac52054c47c0ee89
Bug-Debian: https://bugs.debian.org/919350
Currently the sample hv_get_dhcp_info script only supports the old Red
Hat network-scripts configuration format and leaves everything else to
downstream distributions.
However, Network Manager and systemd-networkd are available across
many distributions, so it makes more sense to implement support for
them here.
Debian's ifupdown is also used in several distributions that are not
Debian derivatives, so I think it makes sense to implement support for
that here too.
Extend the script to support all of these:
- Add a report function that reports the status based on the result of
the previous command
- Add a function for each configuration system that checks whether
that system in use for the given interface, and:
- If so, checks and reports the DHCP status
- If not, returns failure
- Call each of those functions, exiting once one of them succeeds,
with a final fallback to reporting 'Disabled'
The network-scripts check is placed last, because it only checks a
file and not the actual interface state and so is the least reliable
check.
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools-hv-Make-the-sample-hv_get_dhcp_info-script-mor.patch
Ben Hutchings [Sun, 20 Apr 2025 16:50:44 +0000 (18:50 +0200)]
libbpf: Use the standard fixdep build rule
libbpf's all target depends on the fixdep target defined in
tools/scripts/Makefile.include. However the $(BPF_IN_SHARED) and
$(BPF_IN_STATIC) targets don't use it, but instead rebuild fixdep in
the staticobjs or sharedobjs subdirectory using a different command.
Change the $(BPF_IN_SHARED) and $(BPF_IN_STATIC) targets to depend on
fixdep and to symlink the executable into the respective output
subdirectory.
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name libbpf-use-the-standard-fixdep-build-rule.patch
Ben Hutchings [Sun, 23 Mar 2025 20:04:02 +0000 (21:04 +0100)]
[PATCH] perf docs: Fix perf-check manual page built with asciidoctor
Forwarded: https://lore.kernel.org/linux-perf-users/Z-BxCE8WrcRmR_5f@decadent.org.uk/
asciidoctor is more picky than asciidoc about the length of heading
underlines, and currently mis-parses perf-check.txt:
ASCIIDOC perf-check.1
asciidoctor: ERROR: perf-check.txt: line 1: non-conforming manpage title
asciidoctor: ERROR: perf-check.txt: line 1: name section expected
asciidoctor: WARNING: perf-check.txt: line 2: unterminated example block
asciidoctor: WARNING: perf-check.txt: line 5: unterminated listing block
Fix the length of the title underline so it works properly.
Fixes: 98ad0b77323c ("perf check: Introduce 'check' subcommand")
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name perf-docs-Fix-perf-check-manual-page-built-with-asci.patch
Ben Hutchings [Sun, 15 Sep 2024 23:54:24 +0000 (01:54 +0200)]
kbuild, bpf: Fix BTF reproducibility
pahole 1.22 introduced the -j option for parallel processing, and
kbuild uses it, but this makes its output unreproducible.
pahole 1.27 introduced --btf_features=+reproducible_build which makes
the output reproducible even when -j is used.
Assume that if KBUILD_BUILD_TIMESTAMP is set then a reproducible build
is required, and use both options if available or neither if not.
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name kbuild-bpf-fix-btf-reproducibility.patch
Ben Hutchings [Fri, 16 Aug 2024 13:58:04 +0000 (15:58 +0200)]
perf tools: Pass EXTRA_CFLAGS through to libbpf build again
When perf was statically linked to libbpf, any definition of
EXTRA_CFLAGS passed to Makefile.perf propagated to the sub-make of
libbpf. Since commit
9dabf4003423 ("perf python: Switch module to
linking libraries from building source"), EXTRA_CFLAGS is overridden
to "-fPIC" for the sub-make.
Change to include any user-provided EXTRA_CFLAGS before the "-fPIC"
option.
Fixes: 9dabf4003423 ("perf python: Switch module to linking libraries ...")
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name perf-tools-pass-extra_cflags-through-to-libbpf-build-again.patch
Ben Hutchings [Mon, 15 May 2023 13:58:39 +0000 (15:58 +0200)]
perf tools: Support EXTRA_CXXFLAGS
Add support for an EXTRA_CXXFLAGS variable, used similarly to
EXTRA_CFLAGS.
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name perf-tools-support-extra-cxxflags.patch
Uwe Kleine-König [Mon, 24 Apr 2023 10:28:27 +0000 (12:28 +0200)]
tools lib symbol: Use -D_FORTIFY_SOURCE=2 for non-debug builds
Forwarded: https://lore.kernel.org/all/
20230424102827.58707-1-ukleinek@debian.org/
Commit
160be157eaba ("tool lib symbol: Add Makefile/Build") failed to
define _FORTIFY_SOURCE to 2, probabaly this was cut&pasted from other
Makefiles with the same problem.
Fixes: 160be157eaba ("tool lib symbol: Add Makefile/Build")
Signed-off-by: Uwe Kleine-König <ukleinek@debian.org>
Acked-by: Ian Rogers <irogers@google.com>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools_lib_symbol_use_d_fortify_source_2_for_non_debug_builds.patch
Ben Hutchings [Sat, 15 Jan 2022 21:59:11 +0000 (22:59 +0100)]
tools/perf: Fix missing LDFLAGS for some programs
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools-perf-fix-missing-ldflags-for-some-programs.patch
Ben Hutchings [Sat, 15 Jan 2022 21:30:49 +0000 (22:30 +0100)]
libapi: Define _FORTIFY_SOURCE as 2, not empty
Forwarded: https://lore.kernel.org/lkml/
20230424102049.58338-1-ukleinek@debian.org/
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name libapi-define-_fortify_source-as-2-not-empty.patch
Ben Hutchings [Thu, 3 Nov 2016 21:25:26 +0000 (15:25 -0600)]
cpupower: Fix checks for CPU existence
Forwarded: https://lore.kernel.org/all/
20170418023118.GD4152@decadent.org.uk/
Calls to cpufreq_cpu_exists(cpu) were converted to
cpupower_is_cpu_online(cpu) when libcpupower was introduced and the
former function was deleted. However, cpupower_is_cpu_online() does
not distinguish physically absent and offline CPUs, and does not set
errno.
cpufreq-set has already been fixed (commit
c25badc9ceb6).
In cpufreq-bench, which prints an error message for offline CPUs,
properly distinguish and report the zero and negative cases.
Fixes: ac5a181d065d ("cpupower: Add cpuidle parts into library")
Fixes: 53d1cd6b125f ("cpupowerutils: bench - Fix cpu online check")
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
[carnil: Update/Refresh patch for 4.14.17: The issue with the
incorrect check has been fixed with upstream commit
53d1cd6b125f.
Keep in the patch the distinction and report for the zero and
negative cases.]
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name cpupower-fix-checks-for-cpu-existence.patch
Ben Hutchings [Sun, 21 Feb 2016 15:33:15 +0000 (15:33 +0000)]
tools/build: Remove bpf() run-time check at build time
Forwarded: no
It is not correct to test that a syscall works on the build system's
kernel. We might be building on an earlier kernel version or with
security restrictions that block bpf().
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools-build-remove-bpf-run-time-check-at-build-time.patch
Ben Hutchings [Fri, 25 Sep 2015 19:09:23 +0000 (20:09 +0100)]
tools/perf: Remove shebang lines from perf scripts
Forwarded: no
perf scripts need to be invoked through perf, not directly through
perl (or other language interpreter). So including shebang lines in
them is useless and possibly misleading.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools-perf-remove-shebangs.patch
Ben Hutchings [Mon, 8 Sep 2014 17:31:24 +0000 (18:31 +0100)]
kbuild: Fix recordmcount dependency for OOT modules
Forwarded: no
We never rebuild anything in-tree when building an out-of-tree
modules, so external modules should not depend on the recordmcount
sources.
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name kbuild-fix-recordmcount-dependency.patch
Ben Hutchings [Sun, 24 Jun 2012 01:51:39 +0000 (02:51 +0100)]
usbip: Document TCP wrappers
Forwarded: no
Add references to TCP wrappers configuration in the manual page.
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name usbip-document-tcp-wrappers.patch
Ben Hutchings [Fri, 2 Dec 2016 23:06:18 +0000 (23:06 +0000)]
module: Disable matching missing version CRC
Forwarded: not-needed
This partly reverts commit
cd3caefb4663e3811d37cc2afad3cce642d60061.
We want to fail closed if a symbol version CRC is missing, as the
alternative may allow subverting module signing.
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name module-disable-matching-missing-version-crc.patch
Robert Holmes [Tue, 23 Apr 2019 07:39:29 +0000 (07:39 +0000)]
[PATCH] KEYS: Make use of platform keyring for module signature verify
Bug-Debian: https://bugs.debian.org/935945
Bug-Debian: https://bugs.debian.org/
1030200
Origin: https://src.fedoraproject.org/rpms/kernel/raw/master/f/KEYS-Make-use-of-platform-keyring-for-module-signature.patch
Forwarded: https://lore.kernel.org/linux-modules/qvgp2il2co4iyxkzxvcs4p2bpyilqsbfgcprtpfrsajwae2etc@3z2s2o52i3xg/t/#u
This allows a cert in DB to be used to sign modules,
in addition to certs in the MoK and built-in keyrings.
Signed-off-by: Robert Holmes <robeholmes@gmail.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
[bwh: Forward-ported to 5.19: adjust filename]
[наб: reinstate for 6.1, re-write description]
Gbp-Pq: Topic features/all/db-mok-keyring
Gbp-Pq: Name KEYS-Make-use-of-platform-keyring-for-module-signature.patch
Linn Crosetto [Tue, 30 Aug 2016 17:54:38 +0000 (11:54 -0600)]
arm64: add kernel config option to lock down when in Secure Boot mode
Bug-Debian: https://bugs.debian.org/831827
Forwarded: no
Add a kernel configuration option to lock down the kernel, to restrict
userspace's ability to modify the running kernel when UEFI Secure Boot is
enabled. Based on the x86 patch by Matthew Garrett.
Determine the state of Secure Boot in the EFI stub and pass this to the
kernel using the FDT.
Signed-off-by: Linn Crosetto <linn@hpe.com>
[bwh: Forward-ported to 4.10: adjust context]
[Lukas Wunner: Forward-ported to 4.11: drop parts applied upstream]
[bwh: Forward-ported to 4.15 and lockdown patch set:
- Pass result of efi_get_secureboot() in stub through to
efi_set_secure_boot() in main kernel
- Use lockdown API and naming]
[bwh: Forward-ported to 4.19.3: adjust context in update_fdt()]
[dannf: Moved init_lockdown() call after uefi_init(), fixing SB detection]
[bwh: Drop call to init_lockdown(), as efi_set_secure_boot() now calls this]
[bwh: Forward-ported to 5.6: efi_get_secureboot() no longer takes a
sys_table parameter]
[bwh: Forward-ported to 5.7: EFI initialisation from FDT was rewritten, so:
- Add Secure Boot mode to the parameter enumeration in fdtparams.c
- Add a parameter to efi_get_fdt_params() to return the Secure Boot mode
- Since Xen does not have a property name defined for Secure Boot mode,
change efi_get_fdt_prop() to handle a missing property name by clearing
the output variable]
[Salvatore Bonaccorso: Forward-ported to 5.10:
f30f242fb131 ("efi: Rename
arm-init to efi-init common for all arch") renamed arm-init.c to efi-init.c]
Gbp-Pq: Topic features/all/lockdown
Gbp-Pq: Name arm64-add-kernel-config-option-to-lock-down-when.patch
Ben Hutchings [Fri, 30 Aug 2019 14:54:24 +0000 (15:54 +0100)]
mtd: phram,slram: Disable when the kernel is locked down
Forwarded: https://lore.kernel.org/linux-security-module/
20190830154720.eekfjt6c4jzvlbfz@decadent.org.uk/
These drivers allow mapping arbitrary memory ranges as MTD devices.
This should be disabled to preserve the kernel's integrity when it is
locked down.
* Add the HWPARAM flag to the module parameters
* When slram is built-in, it uses __setup() to read kernel parameters,
so add an explicit check security_locked_down() check
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Cc: Matthew Garrett <mjg59@google.com>
Cc: David Howells <dhowells@redhat.com>
Cc: Joern Engel <joern@lazybastard.org>
Cc: linux-mtd@lists.infradead.org
Gbp-Pq: Topic features/all/lockdown
Gbp-Pq: Name mtd-disable-slram-and-phram-when-locked-down.patch
Ben Hutchings [Tue, 10 Sep 2019 10:54:28 +0000 (11:54 +0100)]
efi: Lock down the kernel if booted in secure boot mode
Based on an earlier patch by David Howells, who wrote the following
description:
> UEFI Secure Boot provides a mechanism for ensuring that the firmware will
> only load signed bootloaders and kernels. Certain use cases may also
> require that all kernel modules also be signed. Add a configuration option
> that to lock down the kernel - which includes requiring validly signed
> modules - if the kernel is secure-booted.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
[Salvatore Bonaccorso: After fixing https://bugs.debian.org/956197 the
help text for LOCK_DOWN_IN_EFI_SECURE_BOOT was adjusted to mention that
lockdown is triggered in integrity mode (https://bugs.debian.org/
1025417)]
Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
Gbp-Pq: Topic features/all/lockdown
Gbp-Pq: Name efi-lock-down-the-kernel-if-booted-in-secure-boot-mo.patch
David Howells [Mon, 18 Feb 2019 12:45:03 +0000 (12:45 +0000)]
[28/30] efi: Add an EFI_SECURE_BOOT flag to indicate secure boot mode
Origin: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit?id=
a5d70c55c603233c192b375f72116a395909da28
UEFI machines can be booted in Secure Boot mode. Add an EFI_SECURE_BOOT
flag that can be passed to efi_enabled() to find out whether secure boot is
enabled.
Move the switch-statement in x86's setup_arch() that inteprets the
secure_boot boot parameter to generic code and set the bit there.
Suggested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
cc: linux-efi@vger.kernel.org
[rperier: Forward-ported to 5.5:
- Use pr_warn()
- Adjust context]
[bwh: Forward-ported to 5.6: adjust context]
[bwh: Forward-ported to 5.7:
- Use the next available bit in efi.flags
- Adjust context]
Gbp-Pq: Topic features/all/lockdown
Gbp-Pq: Name efi-add-an-efi_secure_boot-flag-to-indicate-secure-b.patch
Ben Hutchings [Wed, 13 Apr 2016 20:48:06 +0000 (21:48 +0100)]
fs: Add MODULE_SOFTDEP declarations for hard-coded crypto drivers
Bug-Debian: https://bugs.debian.org/819725
Forwarded: https://lore.kernel.org/all/
20160517133631.GF7555@decadent.org.uk/
This helps initramfs builders and other tools to find the full
dependencies of a module.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
[Lukas Wunner: Forward-ported to 4.11: drop parts applied upstream]
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name fs-add-module_softdep-declarations-for-hard-coded-cr.patch
Ian Campbell [Wed, 20 Nov 2013 08:30:14 +0000 (08:30 +0000)]
phy/marvell: disable 4-port phys
Bug-Debian: https://bugs.debian.org/723177
Forwarded: https://lore.kernel.org/netdev/
1386932764.20787.85.camel@dagon.hellion.org.uk/
The Marvell PHY was originally disabled because it can cause networking
failures on some systems. According to Lennert Buytenhek this is because some
of the variants added did not share the same register layout. Since the known
cases are all 4-ports disable those variants (indicated by a 4 in the
penultimate position of the model name) until they can be audited for
correctness.
[bwh: Also #if-out the init functions for these PHYs to avoid
compiler warnings]
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name disable-some-marvell-phys.patch
Ben Hutchings [Mon, 12 Feb 2018 23:59:26 +0000 (23:59 +0000)]
x86: Make x32 syscall support conditional on a kernel parameter
Bug-Debian: https://bugs.debian.org/708070
Forwarded: https://lore.kernel.org/lkml/
1415245982.3398.53.camel@decadent.org.uk/T/#u
Enabling x32 in the standard amd64 kernel would increase its attack
surface while provide no benefit to the vast majority of its users.
No-one seems interested in regularly checking for vulnerabilities
specific to x32 (at least no-one with a white hat).
Still, adding another flavour just to turn on x32 seems wasteful. And
the only differences on syscall entry are a few instructions that mask
out the x32 flag and compare the syscall number.
Use a static key to control whether x32 syscalls are really enabled, a
Kconfig parameter to set its default value and a kernel parameter
"syscall.x32" to change it at boot time.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic features/x86
Gbp-Pq: Name x86-make-x32-syscall-support-conditional.patch
Ben Hutchings [Mon, 5 Dec 2011 04:00:58 +0000 (04:00 +0000)]
x86: memtest: WARN if bad RAM found
Bug-Debian: https://bugs.debian.org/613321
Forwarded: https://lore.kernel.org/all/
20120402150522.GA4980@burratino/
Since this is not a particularly thorough test, if we find any bad
bits of RAM then there is a fair chance that there are other bad bits
we fail to detect.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic features/x86
Gbp-Pq: Name x86-memtest-WARN-if-bad-RAM-found.patch
Geoff Levand [Wed, 13 Jun 2018 17:56:08 +0000 (10:56 -0700)]
arm64/acpi: Add fixup for HPE m400 quirks
Forwarded: https://lore.kernel.org/all/
51d3d738-cdf5-2992-bba5-
c3e1f34096c2@infradead.org/
Adds a new ACPI init routine acpi_fixup_m400_quirks that adds
a work-around for HPE ProLiant m400 APEI firmware problems.
The work-around disables APEI when CONFIG_ACPI_APEI is set and
m400 firmware is detected. Without this fixup m400 systems
experience errors like these on startup:
[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 2
[Hardware Error]: event severity: fatal
[Hardware Error]: Error 0, type: fatal
[Hardware Error]: section_type: memory error
[Hardware Error]: error_status: 0x0000000000001300
[Hardware Error]: error_type: 10, invalid address
Kernel panic - not syncing: Fatal hardware error!
Signed-off-by: Geoff Levand <geoff@infradead.org>
[bwh: Adjust context and indentation to apply to Linux 6.10]
Gbp-Pq: Topic bugfix/arm64
Gbp-Pq: Name arm64-acpi-Add-fixup-for-HPE-m400-quirks.patch
Krzysztof Kozlowski [Wed, 29 Aug 2018 07:32:23 +0000 (09:32 +0200)]
powerpc/boot: Fix missing crc32poly.h when building with KERNEL_XZ
Origin: https://patchwork.ozlabs.org/patch/963258/
After commit
faa16bc404d7 ("lib: Use existing define with
polynomial") the lib/xz/xz_crc32.c includes a header from include/linux
directory thus any other user of this code should define proper include
path.
This fixes the build error on powerpc with CONFIG_KERNEL_XZ:
In file included from ../arch/powerpc/boot/../../../lib/decompress_unxz.c:233:0,
from ../arch/powerpc/boot/decompress.c:42:
../arch/powerpc/boot/../../../lib/xz/xz_crc32.c:18:29: fatal error: linux/crc32poly.h: No such file or directory
Reported-by: Michal Kubecek <mkubecek@suse.cz>
Fixes: faa16bc404d7 ("lib: Use existing define with polynomial")
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Reported-by: kbuild test robot <lkp@intel.com>
Reported-by: Meelis Roos <mroos@linux.ee>
Tested-by: Michal Kubecek <mkubecek@suse.cz>
Gbp-Pq: Topic bugfix/powerpc
Gbp-Pq: Name powerpc-boot-fix-missing-crc32poly.h-when-building-with-kernel_xz.patch
Ben Hutchings [Wed, 11 Jul 2018 22:40:55 +0000 (23:40 +0100)]
ARM: mm: Export __sync_icache_dcache() for xen-privcmd
Forwarded: https://lore.kernel.org/all/
20180711225013.GF14131@decadent.org.uk/
The xen-privcmd driver, which can be modular, calls set_pte_at()
which in turn may call __sync_icache_dcache().
The call to __sync_icache_dcache() may be optimised out because it is
conditional on !pte_special(), and xen-privcmd calls pte_mkspecial().
However, in a non-LPAE configuration there is no "special" bit and the
call is really unconditional.
Fixes: 3ad0876554ca ("xen/privcmd: add IOCTL_PRIVCMD_MMAP_RESOURCE")
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic bugfix/arm
Gbp-Pq: Name arm-mm-export-__sync_icache_dcache-for-xen-privcmd.patch
Ben Hutchings [Sat, 22 Jul 2017 16:37:33 +0000 (17:37 +0100)]
perf tools: Fix unwind build on i386
Forwarded: no
EINVAL may not be defined when building unwind-libunwind.c with
REMOTE_UNWIND_LIBUNWIND, resulting in a compiler error in
LIBUNWIND__ARCH_REG_ID(). Its only caller, access_reg(), only checks
for a negative return value and doesn't care what it is. So change
-EINVAL to -1.
Fixes: 52ffe0ff02fc ("Support x86(32-bit) cross platform callchain unwind.")
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic bugfix/x86
Gbp-Pq: Name perf-tools-fix-unwind-build-on-i386.patch
Ben Hutchings [Fri, 17 Feb 2017 01:30:30 +0000 (01:30 +0000)]
ARM: dts: kirkwood: Fix SATA pinmux-ing for TS419
Forwarded: https://lore.kernel.org/all/
20170218003251.GC4152@decadent.org.uk/
Bug-Debian: https://bugs.debian.org/855017
The old board code for the TS419 assigns MPP pins 15 and 16 as SATA
activity signals (and none as SATA presence signals). Currently the
device tree assigns the SoC's default pinmux groups for SATA, which
conflict with the second Ethernet port.
Reported-by: gmbh@gazeta.pl
Tested-by: gmbh@gazeta.pl
References: https://bugs.debian.org/855017
Cc: stable@vger.kernel.org # 3.15+
Fixes: 934b524b3f49 ("ARM: Kirkwood: Add DT description of QNAP 419")
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic bugfix/arm
Gbp-Pq: Name arm-dts-kirkwood-fix-sata-pinmux-ing-for-ts419.patch
Adam Borowski [Tue, 28 Mar 2017 14:55:05 +0000 (16:55 +0200)]
btrfs: warn about RAID5/6 being experimental at mount time
Bug-Debian: https://bugs.debian.org/863290
Origin: https://bugs.debian.org/863290#5
Forwarded: https://lore.kernel.org/linux-btrfs/
4105665.mVaztBssJx@bagend/
Too many people come complaining about losing their data -- and indeed,
there's no warning outside a wiki and the mailing list tribal knowledge.
Message severity chosen for consistency with XFS -- "alert" makes dmesg
produce nice red background which should get the point across.
Signed-off-by: Adam Borowski <kilobyte@angband.pl>
[bwh: Also add_taint() so this is flagged in bug reports]
[2023-01-10: still accurate according to btrfs-progs own manpage:
https://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git/commit/?id=
922797e15590b836e377d6dc47b828356cafc2a9]
[2024-03-17: still accurate; manpage is now in Documentation/btrfs-man5.rst
implementation went from disk-io.c to super.c; forwarded the issue]
Gbp-Pq: Topic debian
Gbp-Pq: Name btrfs-warn-about-raid5-6-being-experimental-at-mount.patch
Ben Hutchings [Wed, 13 Jul 2016 00:37:22 +0000 (01:37 +0100)]
fanotify: Taint on use of FANOTIFY_ACCESS_PERMISSIONS
Forwarded: not-needed
Various free and proprietary AV products use this feature and users
apparently want it. But punting access checks to userland seems like
an easy way to deadlock the system, and there will be nothing we can
do about that. So warn and taint the kernel if this feature is
actually used.
Gbp-Pq: Topic debian
Gbp-Pq: Name fanotify-taint-on-use-of-fanotify_access_permissions.patch
Ben Hutchings [Sat, 18 Mar 2017 20:47:58 +0000 (20:47 +0000)]
fjes: Disable auto-loading
Bug-Debian: https://bugs.debian.org/853976
Forwarded: no
fjes matches a generic ACPI device ID, and relies on its probe
function to distinguish whether that really corresponds to a supported
device. Very few system will need the driver and it wastes memory on
all the other systems where the same device ID appears, so disable
auto-loading.
Gbp-Pq: Topic debian
Gbp-Pq: Name fjes-disable-autoload.patch
Ben Hutchings [Sat, 20 Apr 2013 14:52:02 +0000 (15:52 +0100)]
viafb: Autoload on OLPC XO 1.5 only
Bug-Debian: https://bugs.debian.org/705788
Forwarded: no
It appears that viafb won't work automatically on all the boards for
which it has a PCI device ID match. Currently, it is blacklisted by
udev along with most other framebuffer drivers, so this doesn't matter
much.
However, this driver is required for console support on the XO 1.5.
We need to allow it to be autoloaded on this model only, and then
un-blacklist it in udev.
Gbp-Pq: Topic bugfix/x86
Gbp-Pq: Name viafb-autoload-on-olpc-xo1.5-only.patch
Ben Hutchings [Wed, 5 Feb 2014 23:01:30 +0000 (23:01 +0000)]
snd-pcsp: Disable autoload
Forwarded: not-needed
Bug-Debian: https://bugs.debian.org/697709
There are two drivers claiming the platform:pcspkr device:
- pcspkr creates an input(!) device that can only beep
- snd-pcsp creates an equivalent input device plus a PCM device that can
play barely recognisable renditions of sampled sound
snd-pcsp is blacklisted by the alsa-base package, but not everyone
installs that. On PCs where no sound is wanted at all, both drivers
will still be loaded and one or other will complain that it couldn't
claim the relevant I/O range.
In case anyone finds snd-pcsp useful, we continue to build it. But
remove the alias, to ensure it's not loaded where it's not wanted.
Gbp-Pq: Topic debian
Gbp-Pq: Name snd-pcsp-disable-autoload.patch
Ben Hutchings [Tue, 20 Aug 2019 23:32:16 +0000 (00:32 +0100)]
intel-iommu: Add Kconfig option to exclude iGPU by default
Bug-Debian: https://bugs.debian.org/935270
Bug-Kali: https://bugs.kali.org/view.php?id=5644
There is still laptop firmware that touches the integrated GPU behind
the operating system's back, and doesn't say so in the RMRR table.
Enabling the IOMMU for all devices causes breakage.
Replace CONFIG_INTEL_IOMMU_DEFAULT_ON with a 3-way choice
corresponding to "on", "off", and "on,intgpu_off".
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic features/x86
Gbp-Pq: Name intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
Ben Hutchings [Tue, 20 Aug 2019 23:05:30 +0000 (00:05 +0100)]
intel-iommu: Add option to exclude integrated GPU only
Bug-Debian: https://bugs.debian.org/935270
Bug-Kali: https://bugs.kali.org/view.php?id=5644
There is still laptop firmware that touches the integrated GPU behind
the operating system's back, and doesn't say so in the RMRR table.
Enabling the IOMMU for all devices causes breakage, but turning it off
for all graphics devices seems like a major weakness.
Add an option, intel_iommu=intgpu_off, to exclude only integrated GPUs
from remapping. This is a narrower exclusion than igfx_off: it only
affects Intel devices on the root bus. Devices attached through an
external port (Thunderbolt or ExpressCard) won't be on the root bus.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic features/x86
Gbp-Pq: Name intel-iommu-add-option-to-exclude-integrated-gpu-only.patch
Ben Hutchings [Mon, 11 Jan 2016 15:23:55 +0000 (15:23 +0000)]
security,perf: Allow further restriction of perf_event_open
Forwarded: https://lore.kernel.org/all/
20160111152355.GS28542@decadent.org.uk/
When kernel.perf_event_open is set to 3 (or greater), disallow all
access to performance events by users without CAP_SYS_ADMIN.
Add a Kconfig symbol CONFIG_SECURITY_PERF_EVENTS_RESTRICT that
makes this value the default.
This is based on a similar feature in grsecurity
(CONFIG_GRKERNSEC_PERF_HARDEN). This version doesn't include making
the variable read-only. It also allows enabling further restriction
at run-time regardless of whether the default is changed.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic features/all
Gbp-Pq: Name security-perf-allow-further-restriction-of-perf_event_open.patch
Serge Hallyn [Fri, 31 May 2013 18:12:12 +0000 (19:12 +0100)]
add sysctl to disallow unprivileged CLONE_NEWUSER by default
Origin: http://kernel.ubuntu.com/git?p=serge%2Fubuntu-saucy.git;a=commit;h=
5c847404dcb2e3195ad0057877e1422ae90892b8
add sysctl to disallow unprivileged CLONE_NEWUSER by default
This is a short-term patch. Unprivileged use of CLONE_NEWUSER
is certainly an intended feature of user namespaces. However
for at least saucy we want to make sure that, if any security
issues are found, we have a fail-safe.
Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
[bwh: Remove unneeded binary sysctl bits]
[bwh: Keep this sysctl, but change the default to enabled]
Gbp-Pq: Topic debian
Gbp-Pq: Name add-sysctl-to-disallow-unprivileged-CLONE_NEWUSER-by-default.patch
Ben Hutchings [Wed, 19 Jun 2013 03:35:28 +0000 (04:35 +0100)]
yama: Disable by default
Bug-Debian: https://bugs.debian.org/712740
Forwarded: not-needed
Gbp-Pq: Topic debian
Gbp-Pq: Name yama-disable-by-default.patch
Ben Hutchings [Fri, 2 Nov 2012 05:32:06 +0000 (05:32 +0000)]
fs: Enable link security restrictions by default
Bug-Debian: https://bugs.debian.org/609455
Forwarded: not-needed
This reverts commit
561ec64ae67ef25cac8d72bb9c4bfc955edfd415
('VFS: don't do protected {sym,hard}links by default').
Gbp-Pq: Topic debian
Gbp-Pq: Name fs-enable-link-security-restrictions-by-default.patch
Ben Hutchings [Sun, 4 Aug 2019 23:29:11 +0000 (00:29 +0100)]
hamradio: Disable auto-loading as mitigation against local exploits
Forwarded: not-needed
We can mitigate the effect of vulnerabilities in obscure protocols by
preventing unprivileged users from loading the modules, so that they
are only exploitable on systems where the administrator has chosen to
load the protocol.
The 'ham' radio protocols (ax25, netrom, rose) are not actively
maintained or widely used. Therefore disable auto-loading.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic debian
Gbp-Pq: Name hamradio-disable-auto-loading-as-mitigation-against-local-exploits.patch
Ben Hutchings [Fri, 19 Nov 2010 02:12:48 +0000 (02:12 +0000)]
[PATCH 1/3] rds: Disable auto-loading as mitigation against local exploits
Forwarded: not-needed
Recent review has revealed several bugs in obscure protocol
implementations that can be exploited by local users for denial of
service or privilege escalation. We can mitigate the effect of any
remaining vulnerabilities in such protocols by preventing unprivileged
users from loading the modules, so that they are only exploitable on
systems where the administrator has chosen to load the protocol.
The 'rds' protocol is one such protocol that has been found to be
vulnerable, and which was not present in the 'lenny' kernel.
Therefore disable auto-loading.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic debian
Gbp-Pq: Name rds-Disable-auto-loading-as-mitigation-against-local.patch
Ben Hutchings [Fri, 19 Nov 2010 02:12:48 +0000 (02:12 +0000)]
[PATCH 2/3] af_802154: Disable auto-loading as mitigation against local exploits
Forwarded: not-needed
Recent review has revealed several bugs in obscure protocol
implementations that can be exploited by local users for denial of
service or privilege escalation. We can mitigate the effect of any
remaining vulnerabilities in such protocols by preventing unprivileged
users from loading the modules, so that they are only exploitable on
systems where the administrator has chosen to load the protocol.
The 'af_802154' (IEEE 802.15.4) protocol is not widely used, was
not present in the 'lenny' kernel, and seems to receive only sporadic
maintenance. Therefore disable auto-loading.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic debian
Gbp-Pq: Name af_802154-Disable-auto-loading-as-mitigation-against.patch
Ben Hutchings [Tue, 8 Jan 2013 03:25:52 +0000 (03:25 +0000)]
radeon, amdgpu: Firmware is required for DRM and KMS on R600 onward
Bug-Debian: https://bugs.debian.org/607194
Bug-Debian: https://bugs.debian.org/607471
Bug-Debian: https://bugs.debian.org/610851
Bug-Debian: https://bugs.debian.org/627497
Bug-Debian: https://bugs.debian.org/632212
Bug-Debian: https://bugs.debian.org/637943
Bug-Debian: https://bugs.debian.org/649448
Bug-Debian: https://bugs.debian.org/697229
Bug-Debian: https://bugs.debian.org/
1053764
Forwarded: no
Last-Update: 2023-11-08
radeon requires firmware/microcode for the GPU in all chips, but for
newer chips (apparently R600 'Evergreen' onward) it also expects
firmware for the memory controller and other sub-blocks.
radeon attempts to gracefully fall back and disable some features if
the firmware is not available, but becomes unstable - the framebuffer
and/or system memory may be corrupted, or the display may stay black.
Therefore, perform a basic check for the existence of
/lib/firmware/radeon when a device is probed, and abort if it
is missing, except for the pre-R600 case.
Update 2023-11-08:
In bug
1053764 Mario Limonciello <mario.limonciello@amd.com> states
that the patch isn't needed anymore for amdgpu, so remove that part
of the patch
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch
Ben Hutchings [Thu, 30 May 2024 12:14:32 +0000 (13:14 +0100)]
firmware_loader: Log direct loading failures as info for d-i
Forwarded: not-needed
On an installed Debian system, firmware packages will normally be
installed automatically based on a mapping of device IDs to firmware.
Within the Debian installer this has not yet happened and we need a
way to detect missing firmware.
Although many/most drivers log firmware loading failures, they do so
using many different formats. This adds a single log message to the
firmware loader, which the installer's hw-detect package will look
for. The log level is set to "info" because some failures are
expected and we do not want to confuse users with bogus error messages
(like in bug #966218).
NOTE: The log message format must not be changed without coordinating
this with the check-missing-firmware.sh in hw-detect.
Gbp-Pq: Topic debian
Gbp-Pq: Name firmware_loader-log-direct-loading-failures-as-info-for-d-i.patch
Ben Hutchings [Sat, 20 Dec 2025 09:15:48 +0000 (10:15 +0100)]
iwlwifi: Do not request unreleased firmware for IWL6000
Bug-Debian: https://bugs.debian.org/689416
Forwarded: not-needed
The iwlwifi driver currently supports firmware API versions 4-6 for
these devices. It will request the file for the latest supported
version and then fall back to earlier versions. However, the latest
version that has actually been released is 4, so we expect the
requests for versions 6 and then 5 to fail.
The installer appears to report any failed request, and it is probably
not easy to detect that this particular failure is harmless. So stop
requesting the unreleased firmware.
Gbp-Pq: Topic debian
Gbp-Pq: Name iwlwifi-do-not-request-unreleased-firmware.patch
Ben Hutchings [Mon, 24 Aug 2009 22:19:58 +0000 (23:19 +0100)]
af9005: Use request_firmware() to load register init script
Forwarded: no
Read the register init script from the Windows driver. This is sick
but should avoid the potential copyright infringement in distributing
a version of the script which is directly derived from the driver.
Gbp-Pq: Topic features/all
Gbp-Pq: Name drivers-media-dvb-usb-af9005-request_firmware.patch
Ben Hutchings [Mon, 29 May 2023 22:16:39 +0000 (00:16 +0200)]
linux-perf: Remove remaining source filenames from executable
When we build perf with -ffile-prefix-map, there are still 2
source directory names embedded in the executable:
1. The Documentation subdirectory, used as a fallback from the
installed location.
2. The python subdirectory, used in the Python script test.
Remove (1) since it is an unnecessary fallback. Change (2)
to the installed location.
Gbp-Pq: Topic debian
Gbp-Pq: Name linux-perf-remove-remaining-source-filenames-from-executable.patch
Ben Hutchings [Sat, 13 May 2023 11:03:26 +0000 (13:03 +0200)]
fixdep: Allow overriding HOSTCC and HOSTLD
Forwarded: not-needed
objtool always uses HOSTCC, HOSTLD, and HOSTAR, so we need to override
these on the command line for cross-builds of linux-kbuild. But it
also builds fixdep which still needs to be native in a cross-build.
Add support for REALHOSTCC and REALHOSTLD variables which, if set,
override HOSTCC and HOSTLD for fixdep only.
Gbp-Pq: Topic debian
Gbp-Pq: Name fixdep-allow-overriding-hostcc-and-hostld.patch
Ben Hutchings [Mon, 16 Sep 2024 17:14:19 +0000 (19:14 +0200)]
Revert "tools build: Clean CFLAGS and LDFLAGS for fixdep"
This reverts commit
5725dd8fa888b4dcdff58241f9d3d3ac42a048e2. That
was a workaround for the bug fixed by commit
6b3db6f9b970 "tools
build: Make fixdep a hostprog" and is no longer needed.
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name revert-tools-build-clean-cflags-and-ldflags-for-fixdep.patch
Ben Hutchings [Thu, 15 Sep 2022 00:14:03 +0000 (02:14 +0200)]
Makefile: Make compiler version comparison optional
Forwarded: not-needed
Bug-Debian: https://bugs.debian.org/
1019749
The top-level Makefile warns if the compiler version string changes at
all between the kernel build and an out-of-tree module build.
We expect that major compiler version changes could introduce ABI
changes, and override the CC variable in out-of-tree module builds to
ensure that the same major compiler version is used. But minor
version changes should not make a difference, so this exact version
comparison produces false warnings.
Since custom kernel packages don't have that, don't remove the version
comparison. Instead, skip it if $(DEBIAN_KERNEL_NO_CC_VERSION_CHECK)
is non-empty.
Gbp-Pq: Topic debian
Gbp-Pq: Name makefile-make-compiler-version-comparison-optional.patch
Ben Hutchings [Mon, 26 Apr 2021 16:27:16 +0000 (18:27 +0200)]
kbuild: Abort build if SUBDIRS used
Forwarded: not-needed
Bug-Debian: https://bugs.debian.org/987575
DKMS and module-assistant both build OOT modules as root. If they
build an old OOT module that still use SUBDIRS this causes Kbuild
to try building a full kernel, which obviously fails but not before
deleting files from the installed headers package.
To avoid such mishaps, detect this situation and abort the build.
The error message is based on that used in commit
0126be38d988
"kbuild: announce removal of SUBDIRS if used".
Gbp-Pq: Topic debian
Gbp-Pq: Name kbuild-abort-build-if-subdirs-used.patch
Ben Hutchings [Thu, 10 Dec 2020 16:31:39 +0000 (17:31 +0100)]
kbuild: Look for module.lds under arch directory too
Forwarded: not-needed
Bug-Debian: https://bugs.debian.org/975571
The module.lds linker script is now built under the scripts directory,
where previously it was under arch/$(SRCARCH).
However, we package the scripts directory as linux-kbuild, which is
meant to be able to do support native and cross-builds. That means it
shouldn't contain files for a specific target architecture without a
wrapper to select between them, and it doesn't appear that linker
scripts are powerful enough to implement such a wrapper.
Building module.lds in a different location would require relatively
large changes. Moving it in the package build rules can work, but we
need to support custom kernel builds from the same source so we can't
assume it's moved.
Therefore, we move module.lds under the arch build directory in
rules.real and change Makefile.modfinal to look for it in both places.
Gbp-Pq: Topic debian
Gbp-Pq: Name kbuild-look-for-module.lds-under-arch-directory-too.patch
Bastian Blank [Tue, 4 Aug 2020 09:44:37 +0000 (09:44 +0000)]
[PATCH 2/2] perf/traceevent: Support asciidoctor for documentation
From
cd02fc78859ef9aefd7c92406f9523622da0b472 Mon Sep 17 00:00:00 2001
Forwarded: not-needed
Gbp-Pq: Topic debian
Gbp-Pq: Name perf-traceevent-support-asciidoctor-for-documentatio.patch
Bastian Blank [Tue, 4 Aug 2020 09:44:19 +0000 (09:44 +0000)]
[PATCH 1/2] Documentation: Drop sphinx version check
From
252aa79fdbd4ac2da09d9b98f81bf11f5e3e1870 Mon Sep 17 00:00:00 2001
Forwarded: not-needed
Gbp-Pq: Topic debian
Gbp-Pq: Name documentation-drop-sphinx-version-check.patch
Ben Hutchings [Tue, 8 Jul 2025 11:30:55 +0000 (13:30 +0200)]
android: Enable building binder as module
Bug-Debian: https://bugs.debian.org/901492
We want to enable use of the Android binder driver to support
Waydroid, but it should not be built-in as that would waste resources
and increase security attack surface on systems that don't need it.
- Change the Makefiles to build the driver as an object with the
"_linux" suffix (which is what Waydroid expects)
- Change config symbol types to tristate
- Add a module description, because modpost warns about missing
descriptions
Gbp-Pq: Topic debian
Gbp-Pq: Name android-enable-building-binder-as-module.patch
Ben Hutchings [Tue, 8 Jul 2025 11:32:21 +0000 (13:32 +0200)]
Export symbols needed by binder
Bug-Debian: https://bugs.debian.org/901492
We want to enable use of the Android binder driver to support
Waydroid, but it should not be built-in as that would waste resources
and increase security attack surface on systems that don't need it.
Export the currently un-exported symbols it depends on.
Gbp-Pq: Topic debian
Gbp-Pq: Name export-symbols-needed-by-binder.patch
Ben Hutchings [Fri, 13 Apr 2018 19:10:28 +0000 (20:10 +0100)]
wireless: Add Debian wireless-regdb certificates
Forwarded: not-needed
This hex dump is generated using:
{
for cert in debian/certs/wireless-regdb-*.pem; do
openssl x509 -in $cert -outform der;
done
} | hexdump -v -e '1/1 "0x%.2x," "\n"' > net/wireless/certs/debian.hex
Gbp-Pq: Topic debian
Gbp-Pq: Name wireless-add-debian-wireless-regdb-certificates.patch
Adriaan Schmidt [Mon, 4 Apr 2022 11:38:33 +0000 (13:38 +0200)]
tools: install perf python bindings
Bug-Debian: http://bugs.debian.org/860957
Forwarded: not-needed
Gbp-Pq: Topic debian
Gbp-Pq: Name tools-perf-install-python-bindings.patch
Ben Hutchings [Mon, 11 May 2015 02:51:07 +0000 (02:51 +0000)]
linux-tools: Install perf-read-vdso{,x}32 in directory under /usr/lib
Gbp-Pq: Topic debian
Gbp-Pq: Name tools-perf-perf-read-vdso-in-libexec.patch
Nobuhiro Iwamatsu [Sat, 20 Dec 2025 09:15:48 +0000 (10:15 +0100)]
[sh4] Fix uImage build
Bug-Debian: https://bugs.debian.org/569034
Forwarded: not-needed
[bwh: This was added without a description, but I think it is done
only to avoid a build-dependency on u-boot-tools.]
Gbp-Pq: Topic debian
Gbp-Pq: Name arch-sh4-fix-uimage-build.patch
YunQiang Su [Mon, 14 May 2018 08:16:18 +0000 (16:16 +0800)]
Enable R2 to R6 emulator by default
Forwarded: not-needed
In upstream code, 'mipsr2emu' kernel option is needed
to enable R2 to R6 emulator. Since we need r6 kernel
for our r2 port, let's always enable it.
Gbp-Pq: Topic debian
Gbp-Pq: Name mips-enable-r2-to-r6-emu-by-default.patch
YunQiang Su [Mon, 16 Nov 2020 01:11:00 +0000 (09:11 +0800)]
Use RELAXED ieee754 mode for Loongson-3 as 3A 4000 is 2008-only
Forwarded: not-needed
There are 2 mode of value of IEEE NaN hardcoded by CPU.
Currently, our mipsel/mips64el port is in so-called lagacy mode.
Loongson 3A 4000 is set as the so-called 2008 mode.
To make Debian workable on Loongson 3A 4000, we need set the kerenl in
RELAXED mode.
https://web.archive.org/web/
20180830093617/https://dmz-portal.mips.com/wiki/MIPS_ABI_-_NaN_Interlinking
[bwh: Update for addition of EMULATED mode in 6.11]
Gbp-Pq: Topic debian
Gbp-Pq: Name mips-ieee754-relaxed.patch
YunQiang Su [Mon, 14 May 2018 08:16:18 +0000 (16:16 +0800)]
Disable uImage generation for mips generic
Forwarded: not-needed
MIPS generic trys to generate uImage when build, which then ask for
u-boot-tools.
[bwh: Updated for 5.17:
- zload-y is no longer assigned here and appears to default to empty
- Adjust context]
Gbp-Pq: Topic debian
Gbp-Pq: Name mips-boston-disable-its.patch
Bastian Blank [Sun, 22 Feb 2009 14:39:35 +0000 (15:39 +0100)]
kbuild: Make the toolchain variables easily overwritable
Forwarded: not-needed
Allow make variables to be overridden for each flavour by a file in
the build tree, .kernelvariables.
We currently use this for ARCH, KERNELRELEASE, CC, and in some cases
also CROSS_COMPILE, KCFLAGS.
This file can only be read after we establish the build tree, and all
use of $(ARCH) needs to be moved after this.
[bwh: Updated for 5.3: include .kernelvariables from current directory
rather than using undefined $(obj).]
[carnil: Update for 6.13: Include .kernelvariables from $(objtree).]
Gbp-Pq: Topic debian
Gbp-Pq: Name kernelvariables.patch
Ben Hutchings [Tue, 12 May 2015 18:29:22 +0000 (19:29 +0100)]
Make mkcompile_h accept an alternate timestamp string
Forwarded: not-needed
We want to include the Debian version in the utsname::version string
instead of a full timestamp string. However, we still need to provide
a standard timestamp string for gen_initramfs_list.sh to make the
kernel image reproducible.
Make mkcompile_h use $KBUILD_BUILD_VERSION_TIMESTAMP in preference to
$KBUILD_BUILD_TIMESTAMP.
Gbp-Pq: Topic debian
Gbp-Pq: Name uname-version-timestamp.patch
Ben Hutchings [Tue, 24 Jul 2012 02:13:10 +0000 (03:13 +0100)]
Include package version along with kernel release in stack traces
Forwarded: not-needed
For distribution binary packages we assume
$DISTRIBUTION_OFFICIAL_BUILD, $DISTRIBUTOR and $DISTRIBUTION_VERSION
are set.
Gbp-Pq: Topic debian
Gbp-Pq: Name version.patch
Ben Hutchings [Sat, 24 Aug 2019 18:00:41 +0000 (19:00 +0100)]
Documentation: Fix broken link to CIPSO draft
Forwarded: not-needed
We exclude the CIPSO draft text as its licence is not DFSG compliant.
Link to the IETF's online version instead.
Gbp-Pq: Topic debian/dfsg
Gbp-Pq: Name documentation-fix-broken-link-to-cipso-draft.patch
Ben Hutchings [Sat, 2 Jun 2012 18:53:38 +0000 (19:53 +0100)]
video: Remove nvidiafb and rivafb
Bug-Debian: https://bugs.debian.org/383481
Forwarded: no
These drivers contain register programming code provided by the
hardware vendor that appears to have been deliberately obfuscated.
This is arguably not the preferred form for modification.
These drivers are also largely redundant with nouveau. The RIVA 128
(NV3) is not supported by nouveau but is about 15 years old and
probably discontinued 10 years ago.
Gbp-Pq: Topic debian/dfsg
Gbp-Pq: Name video-remove-nvidiafb-and-rivafb.patch
Ben Hutchings [Mon, 17 Aug 2009 01:45:41 +0000 (02:45 +0100)]
dvb-usb-af9005: mark as broken
Forwarded: not-needed
Gbp-Pq: Topic debian/dfsg
Gbp-Pq: Name drivers-media-dvb-dvb-usb-af9005-disable.patch
Ben Hutchings [Mon, 13 Apr 2009 16:34:00 +0000 (17:34 +0100)]
Remove microcode patches for mgsuvd (not enabled in Debian configs)
Forwarded: not-needed
Gbp-Pq: Topic debian/dfsg
Gbp-Pq: Name arch-powerpc-platforms-8xx-ucode-disable.patch
Ian Campbell [Thu, 17 Jan 2013 08:55:21 +0000 (08:55 +0000)]
Tweak gitignore for Debian pkg-kernel using git
Forwarded: not-needed
[bwh: Tweak further for pure git]
Gbp-Pq: Topic debian
Gbp-Pq: Name gitignore.patch
Salvatore Bonaccorso [Sat, 20 Dec 2025 09:15:48 +0000 (10:15 +0100)]
linux (6.17.13-1) unstable; urgency=medium
* New upstream stable update:
https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.17.13
- [arm64,armhf] gpu: host1x: Fix race in syncpt alloc/free
- [amd64] accel/ivpu: Ensure rpm_runtime_put in case of engine reset/resume
fail
- [amd64] accel/ivpu: Rework bind/unbind of imported buffers
- [amd64] accel/ivpu: Fix page fault in
ivpu_bo_unbind_all_bos_from_context()
- [amd64] accel/ivpu: Make function parameter names consistent
- [amd64] accel/ivpu: Fix DCT active percent format
- drm/vgem-fence: Fix potential deadlock on release
- bpf: Cleanup unused func args in rqspinlock implementation
- tools/nolibc: handle NULL wstatus argument to waitpid()
- USB: Fix descriptor count when handling invalid MBIM extended descriptor
- perf bpf_counter: Fix opening of "any"(-1) CPU events
- ima: Attach CREDS_CHECK IMA hook to bprm_creds_from_file LSM hook
- [arm64] pinctrl: renesas: rzg2l: Fix PMC restore
- [arm64] clk: renesas: cpg-mssr: Add missing 1ms delay into reset toggle
callback
- [arm64] clk: renesas: cpg-mssr: Read back reset registers to assure values
latched
- HID: logitech-hidpp: Do not assume FAP in hidpp_send_message_sync()
- objtool: Fix standalone --hacks=jump_label
- objtool: Fix weak symbol detection
- [amd64] accel/ivpu: Fix race condition when mapping dmabuf
- perf parse-events: Fix legacy cache events if event is duplicated in a PMU
- wifi: ath10k: move recovery check logic into a new work
- wifi: ath11k: restore register window after global reset
- wifi: ath12k: Fix MSDU buffer types handling in RX error path
- wifi: ath12k: fix VHT MCS assignment
- wifi: ath12k: fix TX and RX MCS rate configurations in HE mode
- sched/fair: Forfeit vruntime on yield
- [arm64,armhf] irqchip/bcm2712-mip: Fix OF node reference imbalance
- [arm64,armhf] irqchip/bcm2712-mip: Fix section mismatch
- [arm64,armhf] irqchip/irq-brcmstb-l2: Fix section mismatch
- [arm64,armhf] irqchip/imx-mu-msi: Fix section mismatch
- [arm64] irqchip/renesas-rzg2l: Fix section mismatch
- [riscv64] irqchip/starfive-jh8100: Fix section mismatch
- [arm64] irqchip/qcom-irq-combiner: Fix section mismatch
- crypto: authenc - Correctly pass EINPROGRESS back up to the caller
- ntfs3: fix uninit memory after failed mi_read in mi_format_new
- ntfs3: Fix uninit buffer allocated by __getname()
- dt-bindings: clock: qcom,x1e80100-gcc: Add missing USB4 clocks/resets
- [arm64] clk: qcom: gcc-x1e80100: Add missing USB4 clocks/resets
- rculist: Add hlist_nulls_replace_rcu() and hlist_nulls_replace_init_rcu()
- inet: Avoid ehash lookup race in inet_ehash_insert()
- inet: Avoid ehash lookup race in inet_twsk_hashdance_schedule()
- [arm64] firmware: qcom: tzmem: fix qcom_tzmem_policy kernel-doc
- crypto: aead - Fix reqsize handling
- block/mq-deadline: Introduce dd_start_request()
- block/mq-deadline: Switch back to a single dispatch list
- [arm64] dts: imx95-15x15-evk: add fan-supply property for pwm-fan
- perf annotate: Check return value of evsel__get_arch() properly
- tty: introduce tty_port_tty guard()
- tty: serial: imx: Only configure the wake register when device is set as
wakeup source
- crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id
- wifi: ath11k: fix VHT MCS assignment
- wifi: ath11k: fix peer HE MCS assignment
- [s390x] smp: Fix fallback CPU detection
- scsi: ufs: core: Move the ufshcd_enable_intr() declaration
- [s390x] ap: Don't leak debug feature files if AP instructions are not
available
- tools/power turbostat: Regression fix Uncore MHz printed in hex
- wifi: ath12k: restore register window after global reset
- leds: upboard: Fix module alias
- PCI: endpoint: pci-epf-test: Fix sleeping function being called from
atomic context
- perf hwmon_pmu: Fix uninitialized variable warning
- phy: mscc: Fix PTP for VSC8574 and VSC8572
- sctp: Defer SCTP_DBG_OBJCNT_DEC() to sctp_destroy_sock().
- [arm64] dts: qcom: qcm2290: Add CCI node
- [arm64] dts: qcom: qcm2290: Fix camss register prop ordering
- RDMA/rxe: Fix null deref on srq->rq.queue after resize failure
- drm/amdgpu: add userq object va track helpers
- drm/amdgpu/userq: fix SDMA and compute validation
- wifi: iwlwifi: mld: add null check for kzalloc() in
iwl_mld_send_proto_offload()
- Revert "mtd: rawnand: marvell: fix layouts"
- mtd: nand: relax ECC parameter validation check
- perf: Remove get_perf_callchain() init_nr argument
- bpf: Refactor stack map trace depth calculation into helper function
- bpf: Fix stackmap overflow check in __bpf_get_stackid()
- [amd64] perf/x86/intel/cstate: Remove PC3 support from LunarLake
- task_work: Fix NMI race condition
- [amd64] x86/dumpstack: Prevent KASAN false positive warnings in
__show_regs()
- [amd64] accel/ivpu: Remove skip of dma unmap for imported buffers
- tools/nolibc/stdio: let perror work when NOLIBC_IGNORE_ERRNO is set
- tools/nolibc/dirent: avoid errno in readdir_r
- [armhf] pinctrl: stm32: fix hwspinlock resource leak in probe function
- drm: nova: select NOVA_CORE
- [amd64] accel/ivpu: Fix race condition when unbinding BOs
- pidfs: add missing PIDFD_INFO_SIZE_VER1
- pidfs: add missing BUILD_BUG_ON() assert on struct pidfd_info
- i3c: fix refcount inconsistency in i3c_master_register
- i3c: master: svc: Prevent incomplete IBI transaction
- random: use offstack cpumask when necessary
- wifi: ath12k: fix potential memory leak in ath12k_wow_arp_ns_offload()
- wifi: ath12k: fix reusing m3 memory
- wifi: ath12k: fix error handling in creating hardware group
- wifi: ath12k: unassign arvif on scan vdev create failure
- [arm64] interconnect: qcom: msm8996: add missing link to SLAVE_USB_HS
- [arm64] dts: qcom: msm8996: add interconnect paths to USB2 controller
- [arm64,armhf] interconnect: debugfs: Fix incorrect error handling for NULL
path
- drm/imagination: Fix reference to devm_platform_get_and_ioremap_resource()
- perf lock contention: Load kernel map before lookup
- perf record: skip synthesize event when open evsel failed
- timers/migration: Convert "while" loops to use "for"
- timers/migration: Remove locking on group connection
- timers/migration: Fix imbalanced NUMA trees
- power: supply: rt5033_charger: Fix device node reference leaks
- power: supply: cw2015: Check devm_delayed_work_autocancel() return code
- power: supply: max17040: Check iio_read_channel_processed() return code
- power: supply: rt9467: Return error on failure in
rt9467_set_value_from_ranges()
- power: supply: rt9467: Prevent using uninitialized local variable in
rt9467_set_value_from_ranges()
- power: supply: wm831x: Check wm831x_set_bits() return value
- power: supply: apm_power: only unset own apm_get_power_status
- scsi: target: Do not write NUL characters into ASCII configfs output
- scsi: target: Fix LUN/device R/W and total command stats
- fs/9p: Don't open remote file with APPEND mode when writeback cache is
used
- [arm64] drm/panthor: Handle errors returned by drm_sched_entity_init()
- [arm64] drm/panthor: Fix group_free_queue() for partially initialized
queues
- [arm64] drm/panthor: Fix UAF race between device unplug and FW event
processing
- [arm64] drm/panthor: Fix race with suspend during unplug
- [arm64] drm/panthor: Fix UAF on kernel BO VA nodes
- [arm64] firmware: ti_sci: Set IO Isolation only if the firmware is capable
- [amd64] iommu/amd: Fix potential out-of-bounds read in iommu_mmio_show
- cleanup: fix scoped_class()
- libbpf: Fix parsing of multi-split BTF
- [armhf] dts: am335x-netcom-plus-2xx: add missing GPIO labels
- [armhf] dts: omap3: beagle-xm: Correct obsolete TWL4030 power compatible
- [armhf] dts: omap3: n900: Correct obsolete TWL4030 power compatible
- entry,unwind/deferred: Fix unwind_reset_info() placement
- coresight: ETR: Fix ETR buffer use-after-free issue
- [amd64] x86/boot: Fix page table access in 5-level to 4-level paging
transition
- efi/libstub: Fix page table access in 5-level to 4-level paging transition
- wifi: rtw89: usb: use common error path for skbs in rtw89_usb_rx_handler()
- wifi: rtw89: usb: fix leak in rtw89_usb_write_port()
- wifi: ath12k: Fix timeout error during beacon stats retrieval
- ext4: correct the checking of quota files before moving extents
- io_uring: use WRITE_ONCE for user shared memory
- [amd64] perf/x86: Fix NULL event access and potential PEBS record loss
- [amd64] perf/x86/intel: Correct large PEBS flag check
- regulator: core: disable supply if enabling main regulator fails
- md: delete mddev kobj before deleting gendisk kobj
- md: fix rcu protection in md_wakeup_thread
- md: avoid repeated calls to del_gendisk
- nbd: defer config put in recv_work
- scsi: stex: Fix reboot_notifier leak in probe error path
- scsi: smartpqi: Fix device resources accessed after device removal
- iio: imu: bmi270: fix dev_err_probe error msg
- dt-bindings: PCI: amlogic: Fix the register name of the DBI region
- RDMA/rtrs: server: Fix error handling in get_or_create_srv
- [arm64,armhf] coresight: tmc: add the handle of the event to the path
- ntfs3: init run lock for extend inode
- [arm64] drm/panthor: Fix potential memleak of vma structure
- scsi: ufs: core: fix incorrect buffer duplication in
ufshcd_read_string_desc()
- md: delete md_redundancy_group when array is becoming inactive
- cpufreq/amd-pstate: Call cppc_set_auto_sel() only for online CPUs
- [powerpc*] kdump: Fix size calculation for hot-removed memory ranges
- [powerpc*] 32: Fix unpaired stwcx. on interrupt exit
- wifi: cw1200: Fix potential memory leak in cw1200_bh_rx_helper()
- nbd: defer config unlock in nbd_genl_connect
- coresight: Change device mode to atomic type
- [arm64] coresight: etm4x: Always set tracer's device mode on target CPU
- [armhf] coresight: etm3x: Always set tracer's device mode on target CPU
- [arm64] coresight: etm4x: Correct polling IDLE bit
- [arm64] coresight: etm4x: Add context synchronization before enabling
trace
- [arm64] coresight: etm4x: Properly control filter in CPU idle with
FEAT_TRF
- perf tools: Fix missing feature check for inherit + SAMPLE_READ
- drm/tidss: Remove max_pclk_khz and min_pclk_khz from tidss display
features
- drm/tidss: Move OLDI mode validation to OLDI bridge mode_valid hook
- [arm64] clk: renesas: r9a09g077: Propagate rate changes to parent clocks
- lib/vsprintf: Check pointer before dereferencing in time_and_date()
- ocfs2: relax BUG() to ocfs2_error() in __ocfs2_move_extent()
- ocfs2: use correct endian in ocfs2_dinode_has_extents
- ACPI: property: Fix fwnode refcount leak in
acpi_fwnode_graph_parse_endpoint()
- scsi: sim710: Fix resource leak by adding missing ioport_unmap() calls
- leds: netxbig: Fix GPIO descriptor leak in error paths
- bpf: Free special fields when update [lru_,]percpu_hash maps
- PCI: keystone: Exit ks_pcie_probe() for invalid mode
- [arm64] dts: rockchip: Move the EEPROM to correct I2C bus on Radxa ROCK 5A
- [arm64] dts: rockchip: Add eeprom vcc-supply for Radxa ROCK 5A
- [arm64] dts: rockchip: Add eeprom vcc-supply for Radxa ROCK 3C
- [amd64] crypto: iaa - Fix incorrect return value in save_iaa_wq()
- [s390x] fpu: Fix false-positive kmsan report in fpu_vstl()
- [arm64] dts: qcom: qrb2210-rb1: Fix UART3 wakeup IRQ storm
- [arm64] drm/msm/dpu: drop dpu_hw_dsc_destroy() prototype
- ps3disk: use memcpy_{from,to}_bvec index
- PCI: Prevent resource tree corruption when BAR resize fails
- bpf: Prevent nesting overflow in bpf_try_get_buffers
- bpf: Handle return value of ftrace_set_filter_ip in register_fentry
- bpf: Check skb->transport_header is set in bpf_skb_check_mtu
- mshv: Fix deposit memory in MSHV_ROOT_HVCALL
- mshv: Fix create memory region overlap check
- watchdog: wdat_wdt: Fix ACPI table leak in probe function
- watchdog: starfive: Fix resource leak in probe error path
- fuse_ctl_add_conn(): fix nlink breakage in case of early failure
- tracefs: fix a leak in eventfs_create_events_dir()
- NFSD/blocklayout: Fix minlength check in proc_layoutget
- [arm64] dts: imx95-tqma9596sa: fix TPM5 pinctrl node name
- [arm64] dts: imx95-tqma9596sa: reduce maximum FlexSPI frequency to 66MHz
- block/blk-throttle: Fix throttle slice time for SSDs
- [arm64] drm/msm: Fix NULL pointer dereference in crashstate_get_vm_logs()
- [arm64] drm/msm: fix missing NULL check after kcalloc in
crashstate_get_bos()
- [arm64] drm/msm/a2xx: stop over-complaining about the legacy firmware
- wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring()
- net: phy: Add helper for fixing RGMII PHY mode based on internal mac delay
- [riscv64] net: stmmac: dwmac-sophgo: Add phy interface filter
- bpf: Fix invalid prog->stats access when update_effective_progs fails
- [powerpc*] 64s/hash: Restrict stress_hpt_struct memblock region to within
RMA limit
- [powerpc*] 64s/ptdump: Fix kernel_hash_pagetable dump for ISA v3.00 HPTE
format
- net: stmmac: Fix VLAN 0 deletion in vlan_del_hw_rx_fltr()
- fs/ntfs3: out1 also needs to put mi
- fs/ntfs3: Prevent memory leaks in add sub record
- [arm64] drm/mediatek: Fix CCORR mtk_ctm_s31_32_to_s1_n function issue
- [arm64] drm/msm/a6xx: Flush LRZ cache before PT switch
- [arm64] drm/msm/a6xx: Fix the gemnoc workaround
- [arm64] drm/msm/a6xx: Improve MX rail fallback in RPMH vote init
- ipv6: clear RA flags when adding a static route (Closes: #
1117959)
- [arm64,armhf] pwm: bcm2835: Make sure the channel is enabled after
pwm_request()
- scsi: ufs: rockchip: Reset controller on PRE_CHANGE of hce enable notify
- scsi: qla2xxx: Fix improper freeing of purex item
- net: phy: realtek: create rtl8211f_config_rgmii_delay()
- [amd64] iommu/vt-d: Fix unused invalidation hint in qi_desc_iotlb
- wifi: mac80211: fix CMAC functions not handling errors
- mfd: mt6397-irq: Fix missing irq_domain_remove() in error path
- mfd: mt6358-irq: Fix missing irq_domain_remove() in error path
- of/fdt: Consolidate duplicate code into helper functions
- of/fdt: Fix incorrect use of dt_root_addr_cells in
early_init_dt_check_kho()
- leds: rgb: leds-qcom-lpg: Don't enable TRILED when configuring PWM
- [arm64] phy: renesas: rcar-gen3-usb2: Fix an error handling path in
rcar_gen3_phy_usb2_probe()
- [arm64] phy: rockchip: naneng-combphy: Add SoC prefix to register
definitions
- [arm64] phy: rockchip: naneng-combphy: Fix PCIe L1ss support RK3562
- [arm64] phy: rockchip: samsung-hdptx: Fix reported clock rate in high bpc
mode
- [arm64] phy: rockchip: samsung-hdptx: Reduce ROPLL loop bandwidth
- [arm64] phy: rockchip: samsung-hdptx: Prevent Inter-Pair Skew from
exceeding the limits
- [amd64] ASoC: SDCA: Fix missing dash in HIDE DisCo property
- net: phy: adin1100: Fix software power-down ready condition
- cpuset: Treat cpusets in attaching as populated
- [riscv64] clk: spacemit: Set clk_hw_onecell_data::num before using flex
array
- wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()
- RAS: Report all ARM processor CPER information to userspace
- ima: Handle error code returned by ima_filter_rule_match()
- usb: chaoskey: fix locking for O_NONBLOCK
- usb: dwc2: fix hang during shutdown if set as peripheral
- usb: dwc2: fix hang during suspend if set as peripheral
- usb: raw-gadget: cap raw_io transfer length to KMALLOC_MAX_SIZE
- regulator: pca9450: Fix error code in probe()
- PM / devfreq: hisi: Fix potential UAF in OPP handling
- [riscv64] KVM: Fix guest page fault within HLV* instructions
- erofs: correct FSDAX detection
- erofs: limit the level of fs stacking for file-backed mounts
- RDMA/bnxt_re: Fix the inline size for GenP7 devices
- RDMA/bnxt_re: Pass correct flag for dma mr creation
- crypto: ahash - Fix crypto_ahash_import with partial block data
- crypto: ahash - Zero positive err value in ahash_update_finish
- ASoC: tas2781: correct the wrong period
- wifi: mt76: mt7996: fix null pointer deref in mt7996_conf_tx()
- wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks
- wifi: mt76: mt7925: add MBSSID support
- wifi: mt76: mt7921: add MBSSID support
- Revert "wifi: mt76: mt792x: improve monitor interface handling"
- wifi: mt76: mt7996: fix max nss value when getting rx chainmask
- wifi: mt76: mt7996: fix implicit beamforming support for mt7992
- wifi: mt76: mt7996: fix several fields in mt7996_mcu_bss_basic_tlv()
- wifi: mt76: mt7996: fix teardown command for an MLD peer
- wifi: mt76: mt7996: set link_valid field when initializing wcid
- wifi: mt76: mt7996: fix MLD group index assignment
- wifi: mt76: mt7996: fix using wrong phy to start in mt7996_mac_restart()
- wifi: mt76: mt7996: grab mt76 mutex in mt7996_mac_sta_event()
- wifi: mt76: mt7996: skip deflink accounting for offchannel links
- wifi: mt76: mt7996: Add missing locking in mt7996_mac_sta_rc_work()
- mt76: mt7615: Fix memory leak in mt7615_mcu_wtbl_sta_add()
- firmware: stratix10-svc: fix make htmldocs warning for stratix10_svc
- [arm64] iommu/arm-smmu-v3: Fix error check in arm_smmu_alloc_cd_tables
- btrfs: fix double free of qgroup record after failure to add delayed ref
head
- btrfs: fix racy bitfield write in btrfs_clear_space_info_full()
- btrfs: fix leaf leak in an error path in btrfs_del_items()
- PCI: dwc: Fix wrong PORT_LOGIC_LTSSM_STATE_MASK definition
- drm/nouveau: restrict the flush page to a 32-bit address
- iomap: always run error completions in user context
- wifi: ieee80211: correct FILS status codes
- backlight: led-bl: Add devlink to supplier LEDs
- backlight: lp855x: Fix lp855x.h kernel-doc warnings
- [arm64] iommu/arm-smmu-qcom: Enable use of all SMR groups when running
bare-metal
- RDMA/irdma: Fix data race in irdma_sc_ccq_arm
- RDMA/irdma: Fix data race in irdma_free_pble
- RDMA/irdma: Do not directly rely on IB_PD_UNSAFE_GLOBAL_RKEY
- [arm64] drm/panthor: Avoid adding of kernel BOs to extobj list
- gfs2: Prevent recursive memory reclaim
- firmware_loader: make RUST_FW_LOADER_ABSTRACTIONS select FW_LOADER
- greybus: gb-beagleplay: Fix timeout handling in bootloader functions
- drm/amd/display: Fix logical vs bitwise bug in
get_embedded_panel_info_v2_1()
- hwmon: sy7636a: Fix regulator_enable resource leak on error path
- ACPI: processor_core: fix map_x2apic_id for amd-pstate on am4
- ublk: prevent invalid access with DEBUG
- ext4: improve integrity checking in __mb_check_buddy by enhancing order-0
validation
- of: Skip devicetree kunit tests when RISCV+ACPI doesn't populate root node
- virtio_vdpa: fix misleading return in void function
- virtio: fix typo in virtio_device_ready() comment
- virtio: fix whitespace in virtio_config_ops
- virtio: fix grammar in virtio_queue_info docs
- virtio: fix virtqueue_set_affinity() docs
- vdpa/mlx5: Fix incorrect error code reporting in query_virtqueues
- vhost: Fix kthread worker cgroup failure handling
- vdpa/pds: use %pe for ERR_PTR() in event handler registration
- virtio: clean up features qword/dword terms
- [amd64] ASoC: Intel: catpt: Fix error path in hw_params()
- [armhf] dts: samsung: universal_c210: turn off SDIO WLAN chip during
system suspend
- [armhf] dts: samsung: exynos4210-i9100: turn off SDIO WLAN chip during
system suspend
- [armhf] dts: samsung: exynos4210-trats: turn off SDIO WLAN chip during
system suspend
- [armhf] dts: samsung: exynos4412-midas: turn off SDIO WLAN chip during
system suspend
- regulator: core: Protect regulator_supply_alias_list with
regulator_list_mutex
- Reinstate "resource: avoid unnecessary lookups in find_next_iomem_res()"
- netfilter: flowtable: check for maximum number of encapsulations in bridge
vlan
- netfilter: nf_conncount: rework API to use sk_buff directly
- netfilter: nft_connlimit: update the count if add was skipped
- iavf: Implement settime64 with -EOPNOTSUPP
- net: stmmac: fix rx limit check in stmmac_rx_zc()
- vfio/pci: Use RCU for error/request triggers to avoid circular locking
- net: phy: aquantia: check for NVMEM deferral
- net: netpoll: initialize work queue before error checks
- mtd: lpddr_cmds: fix signed shifts in lpddr_cmds
- rqspinlock: Enclose lock/unlock within lock entry acquisitions
- rqspinlock: Use trylock fallback when per-CPU rqnode is busy
- [arm64] remoteproc: qcom_q6v5_wcss: fix parsing of qcom,halt-regs
- md/raid5: fix IO hang when array is broken with IO inflight
- [armhf] net: dsa: b53: fix VLAN_ID_IDX write size for BCM5325/65
- [armhf] net: dsa: b53: fix extracting VID from entry for BCM5325/65
- [armhf] net: dsa: b53: b53_arl_read{,25}(): use the entry for comparision
- [armhf] net: dsa: b53: move reading ARL entries into their own function
- [armhf] net: dsa: b53: move writing ARL entries into their own functions
- [armhf] net: dsa: b53: provide accessors for accessing ARL_SRCH_CTL
- [armhf] net: dsa: b53: split reading search entry into their own functions
- [armhf] net: dsa: b53: move ARL entry functions into ops struct
- [armhf] net: dsa: b53: add support for 5389/5397/5398 ARL entry format
- [armhf] net: dsa: b53: use same ARL search result offset for BCM5325/65
- [armhf] net: dsa: b53: fix CPU port unicast ARL entries for BCM5325/65
- [armhf] net: dsa: b53: add support for bcm63xx ARL entry format
- [armhf] net: dsa: b53: fix BCM5325/65 ARL entry multicast port masks
- [armhf] net: dsa: b53: fix BCM5325/65 ARL entry VIDs
- net: hsr: create an API to get hsr port type
- net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop
(CVE-2025-68325)
- perf jitdump: Add sym/str-tables to build-ID generation
- perf tools: Mark split kallsyms DSOs as loaded
- perf tools: Fix split kallsyms DSO counting
- perf hist: In init, ensure mem_info is put on error paths
- [arm64,armhf] pinctrl: single: Fix incorrect type for error return
variable
- 9p: fix cache/debug options printing in v9fs_show_options
- sched/fair: Fix unfairness caused by stalled tg_load_avg_contrib when the
last task migrates out
- sched/core: Fix psi_dequeue() for Proxy Execution
- [amd64] platform/x86:intel/pmc: Update Arrow Lake telemetry GUID
- f2fs: maintain one time GC mode is enabled during whole zoned GC cycle
- rtc: amlogic-a4: fix double free caused by devm
- kbuild: install-extmod-build: Fix when given dir outside the build dir
- kbuild: install-extmod-build: Properly fix CC expansion when ccache is
used
- NFS: Avoid changing nlink when file removes and attribute updates race
- fs/nls: Fix utf16 to utf8 conversion
- NFS: Initialise verifiers for visible dentries in readdir and lookup
- NFS: Initialise verifiers for visible dentries in nfs_atomic_open()
- NFS: Initialise verifiers for visible dentries in _nfs4_open_and_get_state
- NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid
- [arm64] panthor: save task pid and comm in panthor_group
- [arm64] drm/panthor: Prevent potential UAF in group creation
- Revert "nfs: ignore SB_RDONLY when remounting nfs"
- Revert "nfs: clear SB_RDONLY before getting superblock"
- Revert "nfs: ignore SB_RDONLY when mounting nfs"
- NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags
- NFS: Fix inheritance of the block sizes when automounting
- fs/nls: Fix inconsistency between utf8_to_utf32() and utf32_to_utf8()
- [amd64] platform/x86: asus-wmi: use brightness_set_blocking() for kbd led
- [amd64] ASoC: amd: acp: Audio is not resuming after s0ix
- f2fs: revert summary entry count from 2048 to 512 in 16kb block support
- blk-mq: Abort suspend when wakeup events are pending
- block: fix comment for op_is_zone_mgmt() to include RESET_ALL
- block: fix memory leak in __blkdev_issue_zero_pages
- nvme-auth: use kvfree() for memory allocated with kvcalloc()
- drm/plane: Fix IS_ERR() vs NULL check in
drm_plane_create_hotspot_properties()
- regulator: fixed: Rely on the core freeing the enable GPIO
- ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events
- drm/nouveau: refactor deprecated strcpy
- drm/nouveau: fix circular dep oops from vendored i2c encoder
- cifs: Fix handling of a beyond-EOF DIO/unbuffered read over SMB1
- cifs: Fix handling of a beyond-EOF DIO/unbuffered read over SMB2
- docs: hwmon: fix link to g762 devicetree binding
- i2c: spacemit: fix detect issue
- dma/pool: eliminate alloc_pages warning in atomic_pool_expand
- ALSA: uapi: Fix typo in asound.h comment
- drm/amdkfd: Use huge page size to check split svm range alignment
- rtc: gamecube: Check the return value of ioremap()
- rtc: max31335: Fix ignored return value in set_alarm
- ALSA: firewire-motu: add bounds check in put_user loop for DSP events
- drm/xe/fbdev: use the same 64-byte stride alignment as i915
- [amd64] drm/i915/fbdev: make intel_framebuffer_create() error return
handling explicit
- drm/{i915, xe}/fbdev: pass struct drm_device to intel_fbdev_fb_alloc()
- drm/{i915, xe}/fbdev: deduplicate struct drm_mode_fb_cmd2 init
- [amd64] drm/i915/fbdev: Hold runtime PM ref during fbdev BO creation
- block: Use RCU in blk_mq_[un]quiesce_tagset() instead of
set->tag_list_lock
- [amd64] ASoC: amd: acp: update tdm channels for specific DAI
- dm-raid: fix possible NULL dereference with undefined raid type
- dm log-writes: Add missing set_freezable() for freezable kthread
- efi/cper: Add a new helper function to print bitmasks
- efi/cper: Adjust infopfx size to accept an extra space
- efi/cper: align ARM CPER type with UEFI 2.9A/2.10 specs
- scsi: imm: Fix use-after-free bug caused by unfinished delayed work
(CVE-2025-68324)
- perf/core: Fix missing read event generation on task exit
- irqchip/mchp-eic: Fix error code in mchp_eic_domain_alloc()
- cpu: Make atomic hotplug callbacks run with interrupts disabled on UP
- ocfs2: fix memory leak in ocfs2_merge_rec_left()
- [amd64] perf/x86/intel: Fix NULL event dereference crash in
handle_pmi_common()
- usb: gadget: tegra-xudc: Always reinitialize data toggle when clear halt
- usb: typec: ucsi: fix probe failure in gaokun_ucsi_probe()
- usb: phy: Initialize struct usb_phy list_head
- usb: typec: ucsi: fix use-after-free caused by uec->work (CVE-2025-68323)
- usb: dwc3: dwc3_power_off_all_roothub_ports: Use ioremap_np when required
- ALSA: dice: fix buffer overflow in detect_stream_formats()
- ALSA: hda/realtek: Add match for ASUS Xbox Ally projects
- ALSA: hda/tas2781: fix speaker id retrieval for multiple probes
- ALSA: hda: cs35l41: Fix NULL pointer dereference in
cs35l41_hda_read_acpi()
- ALSA: wavefront: Fix integer overflow in sample size validation
[dgit import unpatched linux 6.17.13-1]
Salvatore Bonaccorso [Sat, 20 Dec 2025 09:15:48 +0000 (10:15 +0100)]
Import linux_6.17.13.orig.tar.xz
[dgit import orig linux_6.17.13.orig.tar.xz]
Salvatore Bonaccorso [Sat, 20 Dec 2025 09:15:48 +0000 (10:15 +0100)]
Import linux_6.17.13-1.debian.tar.xz
[dgit import tarball linux 6.17.13-1 linux_6.17.13-1.debian.tar.xz]
Peter Michael Green [Thu, 4 Sep 2025 08:40:00 +0000 (08:40 +0000)]
Manual merge of version 6.12.27-1+rpi1 and 6.12.41-1 to produce 6.12.41-1+rpi1
Salvatore Bonaccorso [Tue, 12 Aug 2025 03:28:04 +0000 (05:28 +0200)]
Merge linux (6.12.41-1) import into refs/heads/workingbranch
Ben Hutchings [Sun, 20 Apr 2025 16:50:44 +0000 (18:50 +0200)]
libbpf: Use the standard fixdep build rule
libbpf's all target depends on the fixdep target defined in
tools/scripts/Makefile.include. However the $(BPF_IN_SHARED) and
$(BPF_IN_STATIC) targets don't use it, but instead rebuild fixdep in
the staticobjs or sharedobjs subdirectory using a different command.
Change the $(BPF_IN_SHARED) and $(BPF_IN_STATIC) targets to depend on
fixdep and to symlink the executable into the respective output
subdirectory.
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name libbpf-use-the-standard-fixdep-build-rule.patch
Ben Hutchings [Sun, 23 Mar 2025 20:04:02 +0000 (21:04 +0100)]
[PATCH] perf docs: Fix perf-check manual page built with asciidoctor
Forwarded: https://lore.kernel.org/linux-perf-users/Z-BxCE8WrcRmR_5f@decadent.org.uk/
asciidoctor is more picky than asciidoc about the length of heading
underlines, and currently mis-parses perf-check.txt:
ASCIIDOC perf-check.1
asciidoctor: ERROR: perf-check.txt: line 1: non-conforming manpage title
asciidoctor: ERROR: perf-check.txt: line 1: name section expected
asciidoctor: WARNING: perf-check.txt: line 2: unterminated example block
asciidoctor: WARNING: perf-check.txt: line 5: unterminated listing block
Fix the length of the title underline so it works properly.
Fixes: 98ad0b77323c ("perf check: Introduce 'check' subcommand")
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name perf-docs-Fix-perf-check-manual-page-built-with-asci.patch
Ben Hutchings [Sun, 15 Sep 2024 23:54:24 +0000 (01:54 +0200)]
kbuild, bpf: Fix BTF reproducibility
pahole 1.22 introduced the -j option for parallel processing, and
kbuild uses it, but this makes its output unreproducible.
pahole 1.27 introduced --btf_features=+reproducible_build which makes
the output reproducible even when -j is used.
Assume that if KBUILD_BUILD_TIMESTAMP is set then a reproducible build
is required, and use both options if available or neither if not.
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name kbuild-bpf-fix-btf-reproducibility.patch
Ben Hutchings [Fri, 16 Aug 2024 13:58:04 +0000 (15:58 +0200)]
perf tools: Pass EXTRA_CFLAGS through to libbpf build again
When perf was statically linked to libbpf, any definition of
EXTRA_CFLAGS passed to Makefile.perf propagated to the sub-make of
libbpf. Since commit
9dabf4003423 ("perf python: Switch module to
linking libraries from building source"), EXTRA_CFLAGS is overridden
to "-fPIC" for the sub-make.
Change to include any user-provided EXTRA_CFLAGS before the "-fPIC"
option.
Fixes: 9dabf4003423 ("perf python: Switch module to linking libraries ...")
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name perf-tools-pass-extra_cflags-through-to-libbpf-build-again.patch
Ben Hutchings [Mon, 15 May 2023 13:58:39 +0000 (15:58 +0200)]
perf tools: Support EXTRA_CXXFLAGS
Add support for an EXTRA_CXXFLAGS variable, used similarly to
EXTRA_CFLAGS.
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name perf-tools-support-extra-cxxflags.patch
Uwe Kleine-König [Mon, 24 Apr 2023 10:28:27 +0000 (12:28 +0200)]
tools lib symbol: Use -D_FORTIFY_SOURCE=2 for non-debug builds
Forwarded: https://lore.kernel.org/all/
20230424102827.58707-1-ukleinek@debian.org/
Commit
160be157eaba ("tool lib symbol: Add Makefile/Build") failed to
define _FORTIFY_SOURCE to 2, probabaly this was cut&pasted from other
Makefiles with the same problem.
Fixes: 160be157eaba ("tool lib symbol: Add Makefile/Build")
Signed-off-by: Uwe Kleine-König <ukleinek@debian.org>
Acked-by: Ian Rogers <irogers@google.com>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools_lib_symbol_use_d_fortify_source_2_for_non_debug_builds.patch
Ben Hutchings [Sat, 15 Jan 2022 21:59:11 +0000 (22:59 +0100)]
tools/perf: Fix missing LDFLAGS for some programs
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools-perf-fix-missing-ldflags-for-some-programs.patch
Ben Hutchings [Sat, 15 Jan 2022 21:30:49 +0000 (22:30 +0100)]
libapi: Define _FORTIFY_SOURCE as 2, not empty
Forwarded: https://lore.kernel.org/lkml/
20230424102049.58338-1-ukleinek@debian.org/
Signed-off-by: Ben Hutchings <benh@debian.org>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name libapi-define-_fortify_source-as-2-not-empty.patch
Ben Hutchings [Thu, 3 Nov 2016 21:25:26 +0000 (15:25 -0600)]
cpupower: Fix checks for CPU existence
Forwarded: https://lore.kernel.org/all/
20170418023118.GD4152@decadent.org.uk/
Calls to cpufreq_cpu_exists(cpu) were converted to
cpupower_is_cpu_online(cpu) when libcpupower was introduced and the
former function was deleted. However, cpupower_is_cpu_online() does
not distinguish physically absent and offline CPUs, and does not set
errno.
cpufreq-set has already been fixed (commit
c25badc9ceb6).
In cpufreq-bench, which prints an error message for offline CPUs,
properly distinguish and report the zero and negative cases.
Fixes: ac5a181d065d ("cpupower: Add cpuidle parts into library")
Fixes: 53d1cd6b125f ("cpupowerutils: bench - Fix cpu online check")
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
[carnil: Update/Refresh patch for 4.14.17: The issue with the
incorrect check has been fixed with upstream commit
53d1cd6b125f.
Keep in the patch the distinction and report for the zero and
negative cases.]
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name cpupower-fix-checks-for-cpu-existence.patch
Ben Hutchings [Sun, 21 Feb 2016 15:33:15 +0000 (15:33 +0000)]
tools/build: Remove bpf() run-time check at build time
Forwarded: no
It is not correct to test that a syscall works on the build system's
kernel. We might be building on an earlier kernel version or with
security restrictions that block bpf().
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools-build-remove-bpf-run-time-check-at-build-time.patch
Ben Hutchings [Fri, 25 Sep 2015 21:50:50 +0000 (22:50 +0100)]
Revert "perf build: Fix libunwind feature detection on 32-bit x86"
Forwarded: no
This reverts commit
05b41775e2edd69a83f592e3534930c934d4038e.
It broke feature detection that was working just fine for us.
Gbp-Pq: Topic bugfix/x86
Gbp-Pq: Name revert-perf-build-fix-libunwind-feature-detection-on.patch
Ben Hutchings [Fri, 25 Sep 2015 19:09:23 +0000 (20:09 +0100)]
tools/perf: Remove shebang lines from perf scripts
Forwarded: no
perf scripts need to be invoked through perf, not directly through
perl (or other language interpreter). So including shebang lines in
them is useless and possibly misleading.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name tools-perf-remove-shebangs.patch
Ben Hutchings [Mon, 8 Sep 2014 17:31:24 +0000 (18:31 +0100)]
kbuild: Fix recordmcount dependency for OOT modules
Forwarded: no
We never rebuild anything in-tree when building an out-of-tree
modules, so external modules should not depend on the recordmcount
sources.
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name kbuild-fix-recordmcount-dependency.patch
Ben Hutchings [Sun, 24 Jun 2012 01:51:39 +0000 (02:51 +0100)]
usbip: Document TCP wrappers
Forwarded: no
Add references to TCP wrappers configuration in the manual page.
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name usbip-document-tcp-wrappers.patch
Ben Hutchings [Fri, 2 Dec 2016 23:06:18 +0000 (23:06 +0000)]
module: Disable matching missing version CRC
Forwarded: not-needed
This partly reverts commit
cd3caefb4663e3811d37cc2afad3cce642d60061.
We want to fail closed if a symbol version CRC is missing, as the
alternative may allow subverting module signing.
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name module-disable-matching-missing-version-crc.patch
Luca Boccassi [Thu, 13 Oct 2022 22:22:06 +0000 (00:22 +0200)]
[PATCH] trust machine keyring (MoK) by default
From
585cbcb982bffc4a8cee2f3d8d099fc64f9a74b9 Mon Sep 17 00:00:00 2001
Forwarded: not-needed
Debian always trusted keys in MoK by default. Upstream made it
conditional on a new EFI variable being set.
To keep backward compatibility skip this check.
Gbp-Pq: Topic features/all/db-mok-keyring
Gbp-Pq: Name trust-machine-keyring-by-default.patch
Robert Holmes [Tue, 23 Apr 2019 07:39:29 +0000 (07:39 +0000)]
[PATCH] KEYS: Make use of platform keyring for module signature verify
Bug-Debian: https://bugs.debian.org/935945
Bug-Debian: https://bugs.debian.org/
1030200
Origin: https://src.fedoraproject.org/rpms/kernel/raw/master/f/KEYS-Make-use-of-platform-keyring-for-module-signature.patch
Forwarded: https://lore.kernel.org/linux-modules/qvgp2il2co4iyxkzxvcs4p2bpyilqsbfgcprtpfrsajwae2etc@3z2s2o52i3xg/t/#u
This allows a cert in DB to be used to sign modules,
in addition to certs in the MoK and built-in keyrings.
Signed-off-by: Robert Holmes <robeholmes@gmail.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
[bwh: Forward-ported to 5.19: adjust filename]
[наб: reinstate for 6.1, re-write description]
Gbp-Pq: Topic features/all/db-mok-keyring
Gbp-Pq: Name KEYS-Make-use-of-platform-keyring-for-module-signature.patch
Lee, Chun-Yi [Tue, 13 Mar 2018 10:38:02 +0000 (18:38 +0800)]
[PATCH 3/4] MODSIGN: checking the blacklisted hash before loading a kernel module
Origin: https://lore.kernel.org/patchwork/patch/933175/
This patch adds the logic for checking the kernel module's hash
base on blacklist. The hash must be generated by sha256 and enrolled
to dbx/mokx.
For example:
sha256sum sample.ko
mokutil --mokx --import-hash $HASH_RESULT
Whether the signature on ko file is stripped or not, the hash can be
compared by kernel.
Cc: David Howells <dhowells@redhat.com>
Cc: Josh Boyer <jwboyer@fedoraproject.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
[Rebased by Luca Boccassi]
[bwh: Forward-ported to 5.19:
- The type parameter to is_hash_blacklisted() is now an enumeration
rather than a string
- Adjust filename, context]
Gbp-Pq: Topic features/all/db-mok-keyring
Gbp-Pq: Name 0003-MODSIGN-checking-the-blacklisted-hash-before-loading-a-kernel-module.patch
Linn Crosetto [Tue, 30 Aug 2016 17:54:38 +0000 (11:54 -0600)]
arm64: add kernel config option to lock down when in Secure Boot mode
Bug-Debian: https://bugs.debian.org/831827
Forwarded: no
Add a kernel configuration option to lock down the kernel, to restrict
userspace's ability to modify the running kernel when UEFI Secure Boot is
enabled. Based on the x86 patch by Matthew Garrett.
Determine the state of Secure Boot in the EFI stub and pass this to the
kernel using the FDT.
Signed-off-by: Linn Crosetto <linn@hpe.com>
[bwh: Forward-ported to 4.10: adjust context]
[Lukas Wunner: Forward-ported to 4.11: drop parts applied upstream]
[bwh: Forward-ported to 4.15 and lockdown patch set:
- Pass result of efi_get_secureboot() in stub through to
efi_set_secure_boot() in main kernel
- Use lockdown API and naming]
[bwh: Forward-ported to 4.19.3: adjust context in update_fdt()]
[dannf: Moved init_lockdown() call after uefi_init(), fixing SB detection]
[bwh: Drop call to init_lockdown(), as efi_set_secure_boot() now calls this]
[bwh: Forward-ported to 5.6: efi_get_secureboot() no longer takes a
sys_table parameter]
[bwh: Forward-ported to 5.7: EFI initialisation from FDT was rewritten, so:
- Add Secure Boot mode to the parameter enumeration in fdtparams.c
- Add a parameter to efi_get_fdt_params() to return the Secure Boot mode
- Since Xen does not have a property name defined for Secure Boot mode,
change efi_get_fdt_prop() to handle a missing property name by clearing
the output variable]
[Salvatore Bonaccorso: Forward-ported to 5.10:
f30f242fb131 ("efi: Rename
arm-init to efi-init common for all arch") renamed arm-init.c to efi-init.c]
Gbp-Pq: Topic features/all/lockdown
Gbp-Pq: Name arm64-add-kernel-config-option-to-lock-down-when.patch