about summary refs log tree commit diff
path: root/pkgs/os-specific/linux/kernel/patches.nix
AgeCommit message (Collapse)AuthorFilesLines
2024-05-03kernelPatches.rust_1_78: initAlyssa Ross1-0/+10
2024-05-03kernelPatches.rust_1_77-6_8,kernelPatches.rust_1_77-6_9: updateAlyssa Ross1-5/+1
Some changes were made when this patch was committed to rust-next. Most importantly, the minimum rustc version was updated from 1.77.0 to 1.77.1, and if we use the latest version of the patch, we'll be able to cleanly apply the 1.78.0 patch. rust-next gets force pushed sometimes[1], so we shouldn't fetch from it in a FOD, hence we now have rust-1.77-6.8.patch in-tree, but this will save us from having rust-1.78.patch in-tree, which we can fetch from lore. [1]: https://github.com/Rust-for-Linux/linux/activity?ref=rust-next
2024-04-08kernelPatches.rust_1_77-6_8,kernelPatches.rust_1_77-6_9: initAlyssa Ross1-0/+14
2024-04-04linux_6_7: dropK9001-9/+0
2024-02-26linux_6_7,linux_testing: patch for Rust 1.76.0Alyssa Ross1-0/+9
2024-01-28linux_6_7: fix Rust support with current rustcAlyssa Ross1-0/+14
The 1.75 patch can't be fetched, because it doesn't apply. But git can apply it cleanly, so it must just need to do a three-way merge or something. Regardless, we need to include a version that patch(1) can apply in Nixpkgs.
2023-10-15linux/patches: remove cpu-cgroup-v2ajs1241-2/+0
2023-09-22linuxKernel.kernels: patch out nvme regression on 2017ish Dell laptopsJade Lovelace1-0/+10
Fixes #253418
2023-07-17linux/patches: drop obsolete CVE-2023-32233 patchMaximilian Bosch1-9/+0
Part of all upstream source-trees kernels we currently build.
2023-07-07linux_5_15: drop fix-amdgpu-5_15 patchFabián Heredia Montiel1-8/+0
2023-06-28linux_5_15: apply patch to fix amdgpuMaximilian Bosch1-0/+8
Closes #240017
2023-05-26Merge remote-tracking branch 'origin/staging-next' into stagingAlyssa Ross1-6/+0
Conflicts: pkgs/os-specific/linux/kernel/patches.nix pkgs/top-level/linux-kernels.nix
2023-05-26kernelPatches.make-maple-state-reusable-after-mas_empty_area: dropAlyssa Ross1-6/+0
No longer used.
2023-05-25kernelPatches.fix-em-ice-bonding: removeAlyssa Ross1-5/+0
This was fixed in 248401cb2c46 ("ice: avoid bonding causing auxiliary plug/unplug under RTNL lock"), which was backported to all relevant kernels.
2023-05-15pkgs/linux: Vendor maple tree patchRobert Hensing1-6/+3
Fetching from a maintainer tree can be unreliable as commits or even repos may be removed.
2023-05-15linux: patch to fix MAP_32BIT crashes, e.g. HaskellRobert Hensing1-0/+9
2023-05-09linux_*, except testing, 4.14: apply patch for CVE-2023-32233Raito Bezarius1-0/+9
This applies the patch for CVE-2023-32233 from kernel 4.19 until 6.3, testing (6.4-rc1 at the moment) is excluded because it already have the fix and 4.14 doesn't have this fix queued for the next stable kernel.
2023-03-13Revert "linux: fix `brcmfmac` driver"K9001-9/+0
This reverts commit 141317dff92656e67ffb726c727766ceffcba52b.
2023-03-12linux: fix `brcmfmac` driverMaximilian Bosch1-0/+9
Reverts a patch that broke WPA auth in offload mode for brcmfmac (broadcom driver). See https://lore.kernel.org/linux-wireless/ZAx0TWRBlGfv7pNl@kroah.com/T/#m0bbd179b92fbbcae0498fd642c31c1ecab1968c0 for context. Had to hack around a bit to make sure this doesn't get applied to hardened which uses an older patch-level without the problematic patch.
2023-02-16linux_{5_15,6_1}: revert patch to fix Equinix Metal bonded networking with ↵Cole Helbling1-0/+5
`ice` driver Some Equinix Metal instances, such as a3.large.x86, m3.large.x86 (specific hardware revisions), and n3.large.x86, use the `ice` kernel driver for their network cards, in conjunction with bonded devices. However, this commit caused a regression where these bonded devices would deadlock. This was initially reported by Jaroslav Pulchart on the netdev mailing list[1], and there were follow-up patches from Dave Ertman[2][3] that attempted to fix this but were not up to snuff for various reasons[4]. Specifically, v2 of the patch ([3]) appears to fix the issue on some devices (tested with 8086:159B network cards), while it is still broken on others (such as an 8086:1593 network card). We revert the patch exposing the issue until upstream has a working solution in order to make Equinix Metal instances work reliably again. [1]: https://lore.kernel.org/netdev/CAK8fFZ6A_Gphw_3-QMGKEFQk=sfCw1Qmq0TVZK3rtAi7vb621A@mail.gmail.com/ [2]: https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20230111183145.1497367-1-david.m.ertman@intel.com/ [3]: https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20230215191757.1826508-1-david.m.ertman@intel.com/ [4]: https://lore.kernel.org/netdev/cb31a911-ba80-e2dc-231f-851757cfd0b8@intel.com/T/#m6e53f8c43093693c10268140126abe99e082dc1c
2022-07-05linux: Remove unused Kernel patchesAndrew Marshall1-46/+0
These are not referenced.
2021-11-03treewide: switch ``builtins.fromJSON(builtins.readFile ./file.json)`` to ↵Sandro Jäckel1-1/+1
lib.importJSON ./file.json
2021-10-20linux: build hardened kernel with matching releasesMaximilian Bosch1-1/+2
Until now we merged kernel updates even if no hardened versions were available yet. On one hand we don't want to delay patch-level updates, on the other hand users of hardened kernels have frequent breakage now[1]. This change aims to provide a solution this issue: * The hardened patchset now references the kernel version it's released for (including a sha256 hash for the fixed-output path of the source tarball). * The `hardenedKernelFor`-function doesn't just append hardened patches now, but also overrides version & src to match the kernel version the patch was built & tested for. Refs #140281 [1] https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.linuxPackages_hardened.kernel.x86_64-linux/all
2021-07-02Revert "linux: fix regression in bridge VLAN configuration"Yurii Matsiuk1-9/+0
This reverts commit 24a08441d52480cf3332a100e24fdf9b83a8351a.
2021-06-21linux: fix regression in bridge VLAN configurationTredwellGit1-0/+9
2021-01-30Merge pull request #108725 from veehaitch/ath_regd_optionalGuillaume Girol1-0/+13
kernelPatches: ath driver: allow setting regulatory domain
2021-01-27kernelPatches: drop export_kernel_fpu_functionsAtemu1-11/+0
Hasn't been necessary since ZFS 0.8.3
2021-01-24linux-hardened: Remove tag patchTim Steinbach1-5/+0
2021-01-11linux: 5.11-rc2 -> 5.11-rc3Tim Steinbach1-10/+0
2021-01-08kernelPatches: ath driver: allow setting regulatory domainVincent Haupert1-0/+13
Ports an OpenWRT patch for Atheros wireless drivers (ath*) which allows the user to change the regulatory domain code to the one which actually applies. All Atheros devices have a regulatory domain burned into their EEPROM. When using a device as AP, this domain is frequently overly restrictive when compared to the regulation which applies in the country the device actually operates in; often, this restriction disallows IR on all channels making it impossible to use the device as an AP at all. This commit introduces the NixOS config option networking.wireless.athUserRegulatoryDomain which, if enabled, applies the patch and sets the kernel config option ATH_USER_REGD. The original OpenWRT patch targets Linux 5.8.
2021-01-07linux-hardened: Track extra versionTim Steinbach1-1/+2
Fixes #108707
2021-01-04linux: 5.11-rc1 -> 5.11-rc2Tim Steinbach1-0/+10
Added temporary patch for a syntax error in the wireless drivers
2020-12-20linux: backport support for RTL8761b to 5.4Eduard Bopp1-0/+7
2020-12-10linux-rt_5_9: export symbols needed by zfsOrivej Desh1-0/+5
Upstream issue: https://github.com/openzfs/zfs/issues/11097#issuecomment-740682245
2020-05-08linux/hardened: move files into directoryEmily1-2/+2
2020-04-23linux_*_hardened: index patches by major kernel versionEmily1-10/+3
This will avoid breaking the build whenever a non-major kernel update happens. In the update script, we map each kernel version to the latest patch for the latest kernel version less than or equal to what we have packaged.
2020-04-17linux_*_hardened: use linux-hardened patch setEmily1-1/+16
This is an updated version of the former upstream, https://github.com/AndroidHardeningArchive/linux-hardened, and provides a minimal set of additional hardening patches on top of upstream. The patch already incorporates many of our hardened profile defaults, and releases are timely (Linux 5.5.15 and 5.6.2 were released on 2020-04-02; linux-hardened patches for them came out on 2020-04-03 and 2020-04-04 respectively).
2020-04-10treewide: Per RFC45, remove all unquoted URLsMichael Reilly1-3/+3
2019-12-22linux: Fix request-key for 4.4 and 4.9Tim Steinbach1-0/+5
2019-12-12linux: patch request-key binary pathKai Wohlfahrt1-0/+5
This is necessary for id mapping to work with NFS + Kerberos, and also touches #68106 and 634638.
2019-10-03linux: update fpu patches for 5.3Jörg Thalheim1-2/+8
At the moment we experience bad instabilities with linux 5.3: https://github.com/zfsonlinux/zfs/issues/9346 as the zfs-native method of disabling the FPU is buggy.
2019-08-31Merge staging-next into stagingFrederik Rietdijk1-0/+6
2019-08-28treewide: remove redundant recvolth1-3/+3
2019-08-20kernelPatches: mac nvme t2 supportSamuel Leathers1-0/+6
2019-05-06linux_5_0: restore __kernel_fpu_{begin,restore}Jörg Thalheim1-0/+5
In 5.0er these function were removed from the public interface also zfs needs them for AVX/AES-NI support. Without this patch for example throughput on a encrypted zfs dataset drops to 200 MB/s from 1.2 GB/s. These functions were removed as their was no user within the linux kernel tree itself.
2019-04-27linux: Remove i2c-oops patchTim Steinbach1-4/+0
2019-04-25Fix kernel oops on boot due to bug in i2c driver.Ambroz Bizjak1-0/+4
https://github.com/NixOS/nixpkgs/issues/60126 https://lkml.org/lkml/2019/4/24/1123 The patch should be removed in the next round of stable releases because the fix should be included. (cherry picked from commit 1e8a0805890fbb1cce1aa751296c82342b0cae7e)
2019-02-18linux: 5.0-rc6 -> 5.0-rc7Tim Steinbach1-7/+0
Also remove interpreter truncation patch, no longer needed in package tree.
2019-02-14linux: allow for interpreter to be truncatedEdmund Wu1-0/+7
via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cb5b020a8d38f77209d0472a0fea755299a8ec78 see https://github.com/NixOS/nixpkgs/issues/53672
2019-02-02linux: Removes the previously removed raspberry pi patchSamuel Dionne-Riel1-8/+0
There seems to have been an oopsie with the rebase.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-01 00:19:31 +0000