Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/sys-fs/zfs-kmod/files
Commit message (Collapse)AuthorAgeFilesLines
* sys-fs/zfs-kmod: backport autotrim CPU fixSam James2024-02-061-0/+31
| | | | | Closes: https://bugs.gentoo.org/923745 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: fix arm64 neon compat w/ >=linux-6.2Sam James2024-01-291-0/+100
| | | | | Closes: https://bugs.gentoo.org/904657 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: drop 2.2.1, 2.2.1-r1Sam James2023-12-281-43/+0
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: drop 2.1.12, 2.1.13, 2.1.13-r1Sam James2023-12-281-40/+0
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: disable zfs_dmu_offset_next_sync tunable by defaultSam James2023-11-242-0/+83
| | | | | | | | | | | | | | | | | | | As a mitigation until more is understood and fixes are tested & reviewed, change the default of zfs_dmu_offset_next_sync from 1 to 0, as it was before 05b3eb6d232009db247882a39d518e7282630753 upstream. There are no reported cases of The Bug being hit with zfs_dmu_offset_next_sync=1: that does not mean this is a cure or a real fix, but it _appears_ to be at least effective in reducing the chances of it happening. By itself, it's a safe change anyway, so it feels worth us doing while we wait. Note that The Bug has been reproduced on 2.1.x as well, hence we do it for both 2.1.13 and 2.2.1. Bug: https://github.com/openzfs/zfs/issues/11900 Bug: https://github.com/openzfs/zfs/issues/15526 Bug: https://bugs.gentoo.org/917224 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: remove unused patchMichael Mair-Keimberger2023-07-051-53/+0
| | | | | | Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at> Closes: https://github.com/gentoo/gentoo/pull/31737 Signed-off-by: Conrad Kostecki <conikost@gentoo.org>
* sys-fs/zfs-kmod: drop 2.1.7, 2.1.10-r1Sam James2023-07-032-284/+0
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: migrate to linux-mod-r1Ionen Wolkens2023-05-301-0/+24
| | | | | | | | | (sam: Taking ionen's PoC conversion and committing it after testing.) Closes: https://bugs.gentoo.org/814194 Closes: https://bugs.gentoo.org/865157 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: revert patch causing SEEK_HOLE corruption (again)Sam James2023-04-161-0/+67
| | | | | | | | | | | | | | | | | | | This reverts commit 4b3133e671b958fa2c915a4faf57812820124a7b upstream. See #14753 - possible corruption again, very similar symptoms to the nightmare that was #11900 and same area of code. We can safely revert it as it's an optimisation rather than a bugfix in itself. Keen Gentoo users may remember the following commits (in Gentoo): - 8e5626dc90e4e6166c2e296371b6ff5a9d13a8c4 - 9fb275f656de639e25acc9497b70b4cae593d35d - 95c250a3f3986b2bc2091dd3981ff1e1d3de0c73 Bug: https://github.com/openzfs/zfs/issues/14753 Bug: https://github.com/openzfs/zfs/issues/11900 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: drop 2.1.8-r1Georgy Yakovlev2023-01-271-14/+0
| | | | Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: revbump 2.1.8, revert 0156253Georgy Yakovlev2023-01-241-0/+14
| | | | Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: add ieee-long-double patch to 2.1.7Georgy Yakovlev2023-01-121-0/+217
| | | | Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: add 2.1.6Sam James2022-10-041-0/+53
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: drop 2.1.4-r1Georgy Yakovlev2022-09-171-304/+0
| | | | Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: drop unused patchGeorgy Yakovlev2022-09-161-74/+0
| | | | Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: backport build fixesSam James2022-06-301-0/+74
| | | | | Closes: https://bugs.gentoo.org/855182 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: drop 0.8.6Georgy Yakovlev2022-06-071-27/+0
| | | | | Bug: https://bugs.gentoo.org/830020 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: backport upstream ZERO_RANGE fixSam James2022-04-221-0/+304
| | | | | Bug: https://github.com/openzfs/zfs/issues/13329 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: remove unused patchMichael Mair-Keimberger2022-04-181-30/+0
| | | | | | | Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at> Closes: https://github.com/gentoo/gentoo/pull/25080 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: fix -Werror issueSam James2022-03-221-0/+30
| | | | | Closes: https://bugs.gentoo.org/835646 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: drop 2.1.1-r4Georgy Yakovlev2021-12-192-625/+0
| | | | Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: revbump 2.1.1 with SEEK/mmap/dnode fixesGeorgy Yakovlev2021-11-102-0/+625
| | | | | | | | take two Bug: https://bugs.gentoo.org/815469 https://github.com/openzfs/zfs/issues/11900 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: yank SEEK_HOLE patch for nowSam James2021-11-081-594/+0
| | | | | | | | | | Preliminary investigation suggests this patch (and earlier iterations) may introduce regressions. Let's yank it for now while we continue the investigation with upstream. Bug: https://bugs.gentoo.org/815469 See: https://github.com/openzfs/zfs/issues/11900 Signed-off-by: Sam James <sam@gentoo.org>
* sys-fs/zfs-kmod: revbump, add HOLE patch and dist-kernel version limitGeorgy Yakovlev2021-11-071-0/+594
| | | | | | | https://github.com/openzfs/zfs/pull/12724 https://github.com/openzfs/zfs/issues/11900 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: drop 2.0.4-r1Georgy Yakovlev2021-07-026-485/+0
| | | | Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: fix a patch that's too largeGeorgy Yakovlev2021-06-081-1231/+0
| | | | | Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: revbump 2.0.4, add 5.12 support and fixesGeorgy Yakovlev2021-06-037-0/+1716
| | | | | | | | run eautoreconf, as a lot of m4 files changed Bug: https://bugs.gentoo.org/792627 Bug: https://bugs.gentoo.org/790686 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: replace sed with a proper patch in 0.8.6Georgy Yakovlev2020-12-181-0/+27
| | | | | Package-Manager: Portage-3.0.12, Repoman-3.0.2 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: drop 0.8.4Georgy Yakovlev2020-11-031-48/+0
| | | | | Package-Manager: Portage-3.0.9, Repoman-3.0.2 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: drop 2.0.0_rc1Georgy Yakovlev2020-09-211-29/+0
| | | | | Package-Manager: Portage-3.0.8, Repoman-3.0.1 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: add powerpc setjmp/longjmp patch to 0.8.4Georgy Yakovlev2020-09-061-0/+48
| | | | | | | | | | | | | | kernel-builtin build fails with powerpc64le-unknown-linux-gnu-ld.bfd: fs/zfs/lua/setjmp/setjmp.o: in function `setjmp': (.text+0x0): multiple definition of `setjmp'; arch/powerpc/kernel/misc.o:(.text+0x30): first defined here powerpc64le-unknown-linux-gnu-ld.bfd: fs/zfs/lua/setjmp/setjmp.o: in function `longjmp': (.text+0x78): multiple definition of `longjmp'; arch/powerpc/kernel/misc.o:(.text+0x9c): first defined here Package-Manager: Portage-3.0.5, Repoman-3.0.1 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: apply znver build failure workaroundGeorgy Yakovlev2020-08-261-0/+29
| | | | | | Bug: https://bugs.gentoo.org/738270 Package-Manager: Portage-3.0.4, Repoman-3.0.1 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: drop 0.8.2Georgy Yakovlev2020-03-301-34/+0
| | | | | Package-Manager: Portage-2.3.96, Repoman-2.3.22 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: revbump 0.8.2, fix O_TMPFILE umask ignoreGeorgy Yakovlev2019-12-131-0/+34
| | | | | | Bug: https://bugs.gentoo.org/686142 Package-Manager: Portage-2.3.79, Repoman-2.3.17 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: drop 0.8.0-r1Georgy Yakovlev2019-06-232-85/+0
| | | | | Package-Manager: Portage-2.3.67, Repoman-2.3.15 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: revbump 0.8.0 with critical patchesGeorgy Yakovlev2019-05-292-0/+85
| | | | | | | | Issue: https://github.com/zfsonlinux/zfs/issues/8816 Issue: https://github.com/zfsonlinux/zfs/issues/8778 Bug: https://bugs.gentoo.org/635002 Package-Manager: Portage-2.3.67, Repoman-2.3.12 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: drop oldGeorgy Yakovlev2019-04-261-31/+0
| | | | | Package-Manager: Portage-2.3.65, Repoman-2.3.12 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs-kmod: 0.7.12 linux-4.20 compatibleGeorgy Yakovlev2019-01-081-0/+31
| | | | | | | backport of current_kernel_time64() fix from 0.7.13-tbr Package-Manager: Portage-2.3.54, Repoman-2.3.12 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
* sys-fs/zfs (and friends): zfs version cleanupJonathan Vasquez2017-11-1720-1566/+0
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.3
* sys-fs/zfs-kmod: removing unused patchesJonathan Vasquez2017-02-123-170/+0
| | | | Package-Manager: Portage-2.3.3, Repoman-2.3.1
* sys-fs/zfs-kmod-0.6.5-r1: Fix discard corruption regressionRichard Yao2015-09-181-0/+31
| | | | | | | | | | This is the first data corruption bug in the history of the ZoL project and I regret to say that it is my fault. I wrote the patch that caused it and it went into HEAD after passing upstream review. It affects Linux 2.6.36 and later. Package-Manager: portage-2.2.20.1 Signed-off-by: Richard Yao <ryao@gentoo.org>
* proj/gentoo: Initial commitRobin H. Johnson2015-08-0822-0/+1705
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed