|
Revision tags: release/13.4.0-p5, release/13.5.0-p1, release/14.2.0-p3, release/13.5.0, release/14.2.0-p2, release/14.1.0-p8, release/13.4.0-p4, release/14.1.0-p7, release/14.2.0-p1, release/13.4.0-p3, release/14.2.0, release/13.4.0, release/14.1.0, release/13.3.0 |
|
| #
052fe26f |
| 13-Dec-2023 |
Dimitry Andric <[email protected]> |
libicp(_rescue)?: use asm versions for all 32-bit arm flavors
OpenZFS upstream refactored the asm versions of sha2 to be usable on all 32-bit arm flavors, so it is not necessary to limit this to arm
libicp(_rescue)?: use asm versions for all 32-bit arm flavors
OpenZFS upstream refactored the asm versions of sha2 to be usable on all 32-bit arm flavors, so it is not necessary to limit this to armv6 and armv7.
Suggested by: jhb
(cherry picked from commit bc6051a060f7f39540e284f2934e61411590dbfd)
show more ...
|
| #
2e4b1bef |
| 08-Dec-2023 |
Dimitry Andric <[email protected]> |
libicp: unbreak for armv6 after recent OpenZFS import
The following upstream commit: 727497ccdfcc module/icp/asm-arm/sha2: enable non-SIMD asm kernels on armv5/6
does indeed enable sha2 asm for ear
libicp: unbreak for armv6 after recent OpenZFS import
The following upstream commit: 727497ccdfcc module/icp/asm-arm/sha2: enable non-SIMD asm kernels on armv5/6
does indeed enable sha2 asm for earlier arm CPUs, but since libicp's Makefile was not updated, this leads to:
ld: error: undefined reference due to --no-allow-shlib-undefined: zfs_sha256_block_armv7
Fix it by compiling sha256-armv7.S and sha512-armv7.S for armv6 too.
Fixes: 3494f7c019fc (cherry picked from commit fb17dfa0c83cc213400fe7e1ed7a39253a4fcefa)
show more ...
|
|
Revision tags: release/14.0.0 |
|
| #
d0b2dbfa |
| 16-Aug-2023 |
Warner Losh <[email protected]> |
Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
|
Revision tags: release/13.2.0, release/12.4.0 |
|
| #
7e3e70ce |
| 22-Nov-2022 |
John Baldwin <[email protected]> |
libicp: Link with -z noexecstack for ld.bfd.
The assembly source files do not contain GNU-stack annotations, so ld.bfd defaults to using an executable stack.
|
| #
a71ea7be |
| 22-Jul-2022 |
Emmanuel Vadot <[email protected]> |
pkgbase: Put zfs utilities and lib in their own package
It is useful to have zfs utilities and lib in a separate package as it allow users to create image that can support ZFS (i.e. not with WITHOUT
pkgbase: Put zfs utilities and lib in their own package
It is useful to have zfs utilities and lib in a separate package as it allow users to create image that can support ZFS (i.e. not with WITHOUT_ZFS in src.conf set) without bloating the default image with all zfs tools (for example for jails).
Differential Revision: https://reviews.freebsd.org/D36225
show more ...
|
| #
9921563f |
| 01-Jul-2022 |
Jessica Clarke <[email protected]> |
libicp: Fix build for powerpc64le
The C sources use the assembly routines for little-endian powerpc64, and the assembly files have ppc64le in their names, but the guard here was for big-endian power
libicp: Fix build for powerpc64le
The C sources use the assembly routines for little-endian powerpc64, and the assembly files have ppc64le in their names, but the guard here was for big-endian powerpc64.
Fixes: 1f1e2261e341 ("zfs: merge openzfs/zfs@deb121309")
show more ...
|
|
Revision tags: release/13.1.0, release/12.3.0, release/13.0.0 |
|
| #
b5fc9e35 |
| 16-Mar-2021 |
Emmanuel Vadot <[email protected]> |
pkgbase: Move libicp in utilities
libicp is used by zdb zhack zinject zstream ztest libzpool.so.2 which are all in FreeBSD-utilities.
Reviewed by: bapt, emaste Differential Revision: https://review
pkgbase: Move libicp in utilities
libicp is used by zdb zhack zinject zstream ztest libzpool.so.2 which are all in FreeBSD-utilities.
Reviewed by: bapt, emaste Differential Revision: https://reviews.freebsd.org/D29164 MFC after: 2 weeks
show more ...
|
|
Revision tags: release/12.2.0 |
|
| #
9e5787d2 |
| 25-Aug-2020 |
Matt Macy <[email protected]> |
Merge OpenZFS support in to HEAD.
The primary benefit is maintaining a completely shared code base with the community allowing FreeBSD to receive new features sooner and with less effort.
I would a
Merge OpenZFS support in to HEAD.
The primary benefit is maintaining a completely shared code base with the community allowing FreeBSD to receive new features sooner and with less effort.
I would advise against doing 'zpool upgrade' or creating indispensable pools using new features until this change has had a month+ to soak.
Work on merging FreeBSD support in to what was at the time "ZFS on Linux" began in August 2018. I first publicly proposed transitioning FreeBSD to (new) OpenZFS on December 18th, 2018. FreeBSD support in OpenZFS was finally completed in December 2019. A CFT for downstreaming OpenZFS support in to FreeBSD was first issued on July 8th. All issues that were reported have been addressed or, for a couple of less critical matters there are pull requests in progress with OpenZFS. iXsystems has tested and dogfooded extensively internally. The TrueNAS 12 release is based on OpenZFS with some additional features that have not yet made it upstream.
Improvements include: project quotas, encrypted datasets, allocation classes, vectorized raidz, vectorized checksums, various command line improvements, zstd compression.
Thanks to those who have helped along the way: Ryan Moeller, Allan Jude, Zack Welch, and many others.
Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D25872
show more ...
|