| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
| |
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Major new features:
- Native encryption
- Device removal
- Allocation classes
- Pool checkpoints
- Sequential scrub and resilver
- Project quota
- Channel programs
- Direct IO
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added support for the bops->check_events() interface which was
added in the 2.6.38 kernel to replace bops->media_changed().
Fully implementing this functionality allows the volume resize
code to rely on revalidate_disk(), which is the preferred
mechanism, and removes the need to use check_disk_size_change().
In order for bops->check_events() to lookup the zvol_state_t
stored in the disk->private_data the zvol_state_lock needs to
be held. Since the check events interface may poll the mutex
has been converted to a rwlock for better concurrently. The
rwlock need only be taken as a writer in the zvol_free() path
when disk->private_data is set to NULL.
The configure checks for the block_device_operations structure
were consolidated in a single kernel-block-device-operations.m4
file.
The ZFS_AC_KERNEL_BDEV_BLOCK_DEVICE_OPERATIONS configure checks
and assoicated dead code was removed. This interface was added
to the 2.6.28 kernel which predates the oldest supported 2.6.32
kernel and will therefore always be available.
Updated maximum Linux version in META file. The 4.17 kernel
was released on 2018-06-03 and ZoL is compatible with the
finalized kernel.
Reviewed-by: Boris Protopopov <[email protected]>
Reviewed-by: Sara Hartse <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #7611
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add META tags Linux-Maximum and Linux-Minimum.
One pain point for package maintainers is ensuring the compatibility of
the packaged version of ZFS with the Linux kernel. By providing an
authoritative compatibility guide in the source tree, maintainers can
automate compatibility checks.
Additionally, increase META string extraction specificity.
configure.ac finds Name and Version by a very simple `grep`, which might
conceivably find other fields. Require the string be at the beginning of
a line, and be followed by a colon to avoid such confusions.
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Giuseppe Di Natale <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Antonio Russo <[email protected]>
Closes #7571
|
|
|
|
|
|
| |
META file and changelog updated.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
|
| |
Fifth release candidate.
Signed-off-by: Brian Behlendorf <[email protected]>
`
|
|
|
|
|
|
| |
Fourth release candidate.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
| |
Third release candidate.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
| |
Second release candidate.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
| |
First release candidate.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
| |
META file and release log updated.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
| |
META file and release log updated.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
|
|
| |
Apply the license specified in the META file to ensure the
compatibility checks are all performed consistently.
Signed-off-by: Brian Behlendorf <[email protected]>
Issue #2757
|
|
|
|
|
|
| |
META file and release log updated.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
| |
META file and release log updated.
Signed-off-by: Brian Behlendorf <[email protected]>
|
|
|
|
|
|
| |
META file and release log updated.
Signed-off-by: Brian Behlendorf <[email protected]>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Create the sixth 0.6.0 release candidate tag (rc6).
|
|
|
|
| |
Create the fifth 0.6.0 release candidate tag (rc5).
|
|
|
|
| |
Create the fourth 0.6.0 release candidate tag (rc4).
|
|
|
|
| |
Create the third 0.6.0 release candidate tag (rc3).
|
|
|
|
| |
Create the second 0.6.0 release candidate tag (rc2).
|
|
|
|
|
|
|
|
| |
Create the first 0.6.0 release candidate tag (rc1). The Posix
layer is now functional and passes fstest and several other
test suites cleanly. We now need this release candidate tag
to broaden the test coverage before we can release the official
zfs-0.6.0.
|
|
|
|
|
| |
Roll the version forward to 0.6.0, the addition of the Posix
layer warrents updating the major version number.
|
|
|
|
| |
Update META file to prep for 0.5.2 tag.
|
| |
|
|
|
|
|
|
| |
Add autoconf style build infrastructure to the ZFS tree. This
includes autogen.sh, configure.ac, m4 macros, some scripts/*,
and makefiles for all the core ZFS components.
|
| |
|
| |
|
|
|