2008-11-20 20:01:55 +00:00
|
|
|
/*
|
|
|
|
* CDDL HEADER START
|
|
|
|
*
|
|
|
|
* The contents of this file are subject to the terms of the
|
|
|
|
* Common Development and Distribution License (the "License").
|
|
|
|
* You may not use this file except in compliance with the License.
|
|
|
|
*
|
|
|
|
* You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
|
|
|
|
* or http://www.opensolaris.org/os/licensing.
|
|
|
|
* See the License for the specific language governing permissions
|
|
|
|
* and limitations under the License.
|
|
|
|
*
|
|
|
|
* When distributing Covered Code, include this CDDL HEADER in each
|
|
|
|
* file and include the License file at usr/src/OPENSOLARIS.LICENSE.
|
|
|
|
* If applicable, add the following below this CDDL HEADER, with the
|
|
|
|
* fields enclosed by brackets "[]" replaced with your own identifying
|
|
|
|
* information: Portions Copyright [yyyy] [name of copyright owner]
|
|
|
|
*
|
|
|
|
* CDDL HEADER END
|
|
|
|
*/
|
|
|
|
/*
|
2010-05-28 20:45:14 +00:00
|
|
|
* Copyright 2009 Sun Microsystems, Inc. All rights reserved.
|
2008-11-20 20:01:55 +00:00
|
|
|
* Use is subject to license terms.
|
|
|
|
*/
|
|
|
|
|
2013-05-06 17:14:52 +00:00
|
|
|
/*
|
2016-10-14 00:59:18 +00:00
|
|
|
* Copyright (c) 2012, 2015 by Delphix. All rights reserved.
|
2013-05-06 17:14:52 +00:00
|
|
|
*/
|
|
|
|
|
2008-11-20 20:01:55 +00:00
|
|
|
#ifndef _ZIO_IMPL_H
|
|
|
|
#define _ZIO_IMPL_H
|
|
|
|
|
|
|
|
#ifdef __cplusplus
|
|
|
|
extern "C" {
|
|
|
|
#endif
|
|
|
|
|
2013-05-10 19:47:54 +00:00
|
|
|
/*
|
2013-07-03 16:13:38 +00:00
|
|
|
* XXX -- Describe ZFS I/O pipeline here. Fill in as needed.
|
2013-05-10 19:47:54 +00:00
|
|
|
*
|
|
|
|
* The ZFS I/O pipeline is comprised of various stages which are defined
|
|
|
|
* in the zio_stage enum below. The individual stages are used to construct
|
|
|
|
* these basic I/O operations: Read, Write, Free, Claim, and Ioctl.
|
|
|
|
*
|
|
|
|
* I/O operations: (XXX - provide detail for each of the operations)
|
|
|
|
*
|
|
|
|
* Read:
|
|
|
|
* Write:
|
|
|
|
* Free:
|
|
|
|
* Claim:
|
|
|
|
* Ioctl:
|
|
|
|
*
|
|
|
|
* Although the most common pipeline are used by the basic I/O operations
|
|
|
|
* above, there are some helper pipelines (one could consider them
|
|
|
|
* sub-pipelines) which are used internally by the ZIO module and are
|
|
|
|
* explained below:
|
|
|
|
*
|
|
|
|
* Interlock Pipeline:
|
|
|
|
* The interlock pipeline is the most basic pipeline and is used by all
|
|
|
|
* of the I/O operations. The interlock pipeline does not perform any I/O
|
|
|
|
* and is used to coordinate the dependencies between I/Os that are being
|
|
|
|
* issued (i.e. the parent/child relationship).
|
|
|
|
*
|
|
|
|
* Vdev child Pipeline:
|
|
|
|
* The vdev child pipeline is responsible for performing the physical I/O.
|
|
|
|
* It is in this pipeline where the I/O are queued and possibly cached.
|
|
|
|
*
|
|
|
|
* In addition to performing I/O, the pipeline is also responsible for
|
|
|
|
* data transformations. The transformations performed are based on the
|
|
|
|
* specific properties that user may have selected and modify the
|
|
|
|
* behavior of the pipeline. Examples of supported transformations are
|
|
|
|
* compression, dedup, and nop writes. Transformations will either modify
|
|
|
|
* the data or the pipeline. This list below further describes each of
|
|
|
|
* the supported transformations:
|
|
|
|
*
|
|
|
|
* Compression:
|
|
|
|
* ZFS supports three different flavors of compression -- gzip, lzjb, and
|
|
|
|
* zle. Compression occurs as part of the write pipeline and is performed
|
|
|
|
* in the ZIO_STAGE_WRITE_BP_INIT stage.
|
|
|
|
*
|
|
|
|
* Dedup:
|
|
|
|
* Dedup reads are handled by the ZIO_STAGE_DDT_READ_START and
|
|
|
|
* ZIO_STAGE_DDT_READ_DONE stages. These stages are added to an existing
|
|
|
|
* read pipeline if the dedup bit is set on the block pointer.
|
|
|
|
* Writing a dedup block is performed by the ZIO_STAGE_DDT_WRITE stage
|
|
|
|
* and added to a write pipeline if a user has enabled dedup on that
|
|
|
|
* particular dataset.
|
|
|
|
*
|
|
|
|
* NOP Write:
|
|
|
|
* The NOP write feature is performed by the ZIO_STAGE_NOP_WRITE stage
|
2019-08-30 16:53:15 +00:00
|
|
|
* and is added to an existing write pipeline if a cryptographically
|
2013-05-10 19:47:54 +00:00
|
|
|
* secure checksum (i.e. SHA256) is enabled and compression is turned on.
|
|
|
|
* The NOP write stage will compare the checksums of the current data
|
|
|
|
* on-disk (level-0 blocks only) and the data that is currently being written.
|
|
|
|
* If the checksum values are identical then the pipeline is converted to
|
|
|
|
* an interlock pipeline skipping block allocation and bypassing the
|
|
|
|
* physical I/O. The nop write feature can handle writes in either
|
|
|
|
* syncing or open context (i.e. zil writes) and as a result is mutually
|
|
|
|
* exclusive with dedup.
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
*
|
|
|
|
* Encryption:
|
|
|
|
* Encryption and authentication is handled by the ZIO_STAGE_ENCRYPT stage.
|
|
|
|
* This stage determines how the encryption metadata is stored in the bp.
|
|
|
|
* Decryption and MAC verification is performed during zio_decrypt() as a
|
|
|
|
* transform callback. Encryption is mutually exclusive with nopwrite, because
|
|
|
|
* blocks with the same plaintext will be encrypted with different salts and
|
|
|
|
* IV's (if dedup is off), and therefore have different ciphertexts. For dedup
|
|
|
|
* blocks we deterministically generate the IV and salt by performing an HMAC
|
|
|
|
* of the plaintext, which is computationally expensive, but allows us to keep
|
|
|
|
* support for encrypted dedup. See the block comment in zio_crypt.c for
|
|
|
|
* details.
|
2013-05-10 19:47:54 +00:00
|
|
|
*/
|
|
|
|
|
2008-11-20 20:01:55 +00:00
|
|
|
/*
|
2010-05-28 20:45:14 +00:00
|
|
|
* zio pipeline stage definitions
|
2008-11-20 20:01:55 +00:00
|
|
|
*/
|
2010-05-28 20:45:14 +00:00
|
|
|
enum zio_stage {
|
|
|
|
ZIO_STAGE_OPEN = 1 << 0, /* RWFCI */
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
ZIO_STAGE_READ_BP_INIT = 1 << 1, /* R---- */
|
2016-10-14 00:59:18 +00:00
|
|
|
ZIO_STAGE_WRITE_BP_INIT = 1 << 2, /* -W--- */
|
|
|
|
ZIO_STAGE_FREE_BP_INIT = 1 << 3, /* --F-- */
|
|
|
|
ZIO_STAGE_ISSUE_ASYNC = 1 << 4, /* RWF-- */
|
|
|
|
ZIO_STAGE_WRITE_COMPRESS = 1 << 5, /* -W--- */
|
2008-12-03 20:09:06 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_ENCRYPT = 1 << 6, /* -W--- */
|
|
|
|
ZIO_STAGE_CHECKSUM_GENERATE = 1 << 7, /* -W--- */
|
2008-12-03 20:09:06 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_NOP_WRITE = 1 << 8, /* -W--- */
|
2013-05-10 19:47:54 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_DDT_READ_START = 1 << 9, /* R---- */
|
|
|
|
ZIO_STAGE_DDT_READ_DONE = 1 << 10, /* R---- */
|
|
|
|
ZIO_STAGE_DDT_WRITE = 1 << 11, /* -W--- */
|
|
|
|
ZIO_STAGE_DDT_FREE = 1 << 12, /* --F-- */
|
2008-11-20 20:01:55 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_GANG_ASSEMBLE = 1 << 13, /* RWFC- */
|
|
|
|
ZIO_STAGE_GANG_ISSUE = 1 << 14, /* RWFC- */
|
2008-11-20 20:01:55 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_DVA_THROTTLE = 1 << 15, /* -W--- */
|
|
|
|
ZIO_STAGE_DVA_ALLOCATE = 1 << 16, /* -W--- */
|
|
|
|
ZIO_STAGE_DVA_FREE = 1 << 17, /* --F-- */
|
|
|
|
ZIO_STAGE_DVA_CLAIM = 1 << 18, /* ---C- */
|
2008-11-20 20:01:55 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_READY = 1 << 19, /* RWFCI */
|
2008-11-20 20:01:55 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_VDEV_IO_START = 1 << 20, /* RW--I */
|
|
|
|
ZIO_STAGE_VDEV_IO_DONE = 1 << 21, /* RW--I */
|
|
|
|
ZIO_STAGE_VDEV_IO_ASSESS = 1 << 22, /* RW--I */
|
2008-11-20 20:01:55 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_CHECKSUM_VERIFY = 1 << 23, /* R---- */
|
2008-11-20 20:01:55 +00:00
|
|
|
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_DONE = 1 << 24 /* RWFCI */
|
2010-05-28 20:45:14 +00:00
|
|
|
};
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_INTERLOCK_STAGES \
|
|
|
|
(ZIO_STAGE_READY | \
|
|
|
|
ZIO_STAGE_DONE)
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_INTERLOCK_PIPELINE \
|
2008-12-03 20:09:06 +00:00
|
|
|
ZIO_INTERLOCK_STAGES
|
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_VDEV_IO_STAGES \
|
|
|
|
(ZIO_STAGE_VDEV_IO_START | \
|
|
|
|
ZIO_STAGE_VDEV_IO_DONE | \
|
|
|
|
ZIO_STAGE_VDEV_IO_ASSESS)
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_VDEV_CHILD_PIPELINE \
|
|
|
|
(ZIO_VDEV_IO_STAGES | \
|
|
|
|
ZIO_STAGE_DONE)
|
2008-12-03 20:09:06 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_READ_COMMON_STAGES \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_VDEV_IO_STAGES | \
|
|
|
|
ZIO_STAGE_CHECKSUM_VERIFY)
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_READ_PHYS_PIPELINE \
|
2008-12-03 20:09:06 +00:00
|
|
|
ZIO_READ_COMMON_STAGES
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_READ_PIPELINE \
|
|
|
|
(ZIO_READ_COMMON_STAGES | \
|
|
|
|
ZIO_STAGE_READ_BP_INIT)
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_DDT_CHILD_READ_PIPELINE \
|
|
|
|
ZIO_READ_COMMON_STAGES
|
2008-12-03 20:09:06 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_DDT_READ_PIPELINE \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_STAGE_READ_BP_INIT | \
|
|
|
|
ZIO_STAGE_DDT_READ_START | \
|
|
|
|
ZIO_STAGE_DDT_READ_DONE)
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_WRITE_COMMON_STAGES \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_VDEV_IO_STAGES | \
|
|
|
|
ZIO_STAGE_ISSUE_ASYNC | \
|
|
|
|
ZIO_STAGE_CHECKSUM_GENERATE)
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_WRITE_PHYS_PIPELINE \
|
|
|
|
ZIO_WRITE_COMMON_STAGES
|
2008-11-20 20:01:55 +00:00
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_REWRITE_PIPELINE \
|
|
|
|
(ZIO_WRITE_COMMON_STAGES | \
|
2016-10-14 00:59:18 +00:00
|
|
|
ZIO_STAGE_WRITE_COMPRESS | \
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_ENCRYPT | \
|
2010-05-28 20:45:14 +00:00
|
|
|
ZIO_STAGE_WRITE_BP_INIT)
|
|
|
|
|
|
|
|
#define ZIO_WRITE_PIPELINE \
|
|
|
|
(ZIO_WRITE_COMMON_STAGES | \
|
|
|
|
ZIO_STAGE_WRITE_BP_INIT | \
|
2016-10-14 00:59:18 +00:00
|
|
|
ZIO_STAGE_WRITE_COMPRESS | \
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_ENCRYPT | \
|
2016-10-14 00:59:18 +00:00
|
|
|
ZIO_STAGE_DVA_THROTTLE | \
|
2010-05-28 20:45:14 +00:00
|
|
|
ZIO_STAGE_DVA_ALLOCATE)
|
|
|
|
|
|
|
|
#define ZIO_DDT_CHILD_WRITE_PIPELINE \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_VDEV_IO_STAGES | \
|
2016-10-14 00:59:18 +00:00
|
|
|
ZIO_STAGE_DVA_THROTTLE | \
|
2010-05-28 20:45:14 +00:00
|
|
|
ZIO_STAGE_DVA_ALLOCATE)
|
|
|
|
|
|
|
|
#define ZIO_DDT_WRITE_PIPELINE \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_STAGE_WRITE_BP_INIT | \
|
2016-10-14 00:59:18 +00:00
|
|
|
ZIO_STAGE_ISSUE_ASYNC | \
|
|
|
|
ZIO_STAGE_WRITE_COMPRESS | \
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
ZIO_STAGE_ENCRYPT | \
|
2010-05-28 20:45:14 +00:00
|
|
|
ZIO_STAGE_CHECKSUM_GENERATE | \
|
|
|
|
ZIO_STAGE_DDT_WRITE)
|
|
|
|
|
|
|
|
#define ZIO_GANG_STAGES \
|
|
|
|
(ZIO_STAGE_GANG_ASSEMBLE | \
|
|
|
|
ZIO_STAGE_GANG_ISSUE)
|
|
|
|
|
|
|
|
#define ZIO_FREE_PIPELINE \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_STAGE_FREE_BP_INIT | \
|
|
|
|
ZIO_STAGE_DVA_FREE)
|
|
|
|
|
|
|
|
#define ZIO_DDT_FREE_PIPELINE \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_STAGE_FREE_BP_INIT | \
|
|
|
|
ZIO_STAGE_ISSUE_ASYNC | \
|
|
|
|
ZIO_STAGE_DDT_FREE)
|
|
|
|
|
|
|
|
#define ZIO_CLAIM_PIPELINE \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_STAGE_DVA_CLAIM)
|
|
|
|
|
|
|
|
#define ZIO_IOCTL_PIPELINE \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_STAGE_VDEV_IO_START | \
|
|
|
|
ZIO_STAGE_VDEV_IO_ASSESS)
|
|
|
|
|
2019-03-29 16:13:20 +00:00
|
|
|
#define ZIO_TRIM_PIPELINE \
|
|
|
|
(ZIO_INTERLOCK_STAGES | \
|
|
|
|
ZIO_STAGE_ISSUE_ASYNC | \
|
|
|
|
ZIO_VDEV_IO_STAGES)
|
|
|
|
|
2010-05-28 20:45:14 +00:00
|
|
|
#define ZIO_BLOCKING_STAGES \
|
|
|
|
(ZIO_STAGE_DVA_ALLOCATE | \
|
|
|
|
ZIO_STAGE_DVA_CLAIM | \
|
|
|
|
ZIO_STAGE_VDEV_IO_START)
|
2008-11-20 20:01:55 +00:00
|
|
|
|
|
|
|
extern void zio_inject_init(void);
|
|
|
|
extern void zio_inject_fini(void);
|
|
|
|
|
|
|
|
#ifdef __cplusplus
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#endif /* _ZIO_IMPL_H */
|