Filesystem Crypto
[Prev Page][Next Page]
- [PATCH v3 04/10] common/verity: add _filter_fsverity_digest()
- [PATCH v3 09/10] generic/624: test multiple Merkle tree block sizes
- [PATCH v3 07/10] generic/577: support non-4K Merkle tree block size
- [PATCH v3 05/10] generic/572: support non-4K Merkle tree block size
- [PATCH v3 06/10] generic/573: support non-4K Merkle tree block size
- [PATCH v3 00/10] xfstests: update verity tests for non-4K block and page size
- Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
- Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
- Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
- Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
- [PATCH v2 07/11] fsverity: support enabling with tree block size < PAGE_SIZE
- [PATCH v2 03/11] fsverity: store log2(digest_size) precomputed
- [PATCH v2 10/11] fs/buffer.c: support fsverity in block_read_full_folio()
- [PATCH v2 11/11] ext4: allow verity with fs block size < PAGE_SIZE
- [PATCH v2 04/11] fsverity: use EFBIG for file too large to enable verity
- [PATCH v2 08/11] ext4: simplify ext4_readpage_limit()
- [PATCH v2 09/11] f2fs: simplify f2fs_readpage_limit()
- [PATCH v2 06/11] fsverity: support verification with tree block size < PAGE_SIZE
- [PATCH v2 05/11] fsverity: replace fsverity_hash_page() with fsverity_hash_block()
- [PATCH v2 02/11] fsverity: simplify Merkle tree readahead size calculation
- [PATCH v2 00/11] fsverity: support for non-4K pages
- [PATCH v2 01/11] fsverity: use unsigned long for level_start
- [PATCH v2 05/10] generic/572: support non-4K Merkle tree block size
- [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
- [PATCH v2 04/10] common/verity: add _filter_fsverity_digest()
- [PATCH v2 03/10] common/verity: use FSV_BLOCK_SIZE by default
- [PATCH v2 10/10] generic/575: test 1K Merkle tree block size
- [PATCH v2 09/10] generic/624: test multiple Merkle tree block sizes
- [PATCH v2 07/10] generic/577: support non-4K Merkle tree block size
- [PATCH v2 02/10] common/verity: set FSV_BLOCK_SIZE to an appropriate value
- [PATCH v2 01/10] common/verity: add and use _fsv_can_enable()
- [PATCH v2 06/10] generic/573: support non-4K Merkle tree block size
- [PATCH v2 00/10] xfstests: update verity tests for non-4K block and page size
- Re: Separate mailing list (and git and patchwork) for fsverity?
- Re: [RFC] fs-verity and encryption for EROFS
- Re: Separate mailing list (and git and patchwork) for fsverity?
- [RFC] fs-verity and encryption for EROFS
- Re: [PATCH 09/10] generic/624: test multiple Merkle tree block sizes
- Re: [PATCH 09/10] generic/624: test multiple Merkle tree block sizes
- Re: [PATCH 09/10] generic/624: test multiple Merkle tree block sizes
- Re: [PATCH] fsverity: don't check builtin signatures when require_signatures=0
- Re: [PATCH] fsverity: don't check builtin signatures when require_signatures=0
- Re: [PATCH] fsverity: mark builtin signatures as deprecated
- Re: [PATCH] fsverity: don't check builtin signatures when require_signatures=0
- Re: [PATCH] fsverity: mark builtin signatures as deprecated
- Re: [PATCH] fsverity: mark builtin signatures as deprecated
- [RFC PATCH v7 2/4] blk-crypto: show supported key types in sysfs
- [RFC PATCH v7 1/4] blk-crypto: add basic hardware-wrapped key support
- [RFC PATCH v7 4/4] fscrypt: add support for hardware-wrapped keys
- [RFC PATCH v7 3/4] blk-crypto: add ioctls to create and prepare hardware-wrapped keys
- [RFC PATCH v7 0/4] Support for hardware-wrapped inline encryption keys
- [PATCH] fsverity: remove debug messages and CONFIG_FS_VERITY_DEBUG
- Re: [PATCH 0/4] fsverity cleanups
- [PATCH 2/4] fsverity: optimize fsverity_prepare_setattr() on non-verity files
- [PATCH 4/4] fsverity: pass pos and size to ->write_merkle_tree_block
- [PATCH 3/4] fsverity: optimize fsverity_cleanup_inode() on non-verity files
- [PATCH 0/4] fsverity cleanups
- [PATCH 1/4] fsverity: optimize fsverity_file_open() on non-verity files
- Re: [PATCH] fscrypt: Fix null pointer when defer i_crypt_info
- Re: [PATCH] fscrypt: Fix null pointer when defer i_crypt_info
- Separate mailing list (and git and patchwork) for fsverity?
- Re: [PATCH] fscrypt: Fix null pointer when defer i_crypt_info
- [PATCH] fscrypt: Fix null pointer when defer i_crypt_info
- Re: [GIT PULL] fsverity updates for 6.2
- Re: [GIT PULL] fscrypt updates for 6.2
- [GIT PULL] fsverity updates for 6.2
- [GIT PULL] fscrypt updates for 6.2
- [PATCH 08/10] generic/574: test multiple Merkle tree block sizes
- [PATCH 03/10] common/verity: use FSV_BLOCK_SIZE by default
- [PATCH 05/10] generic/572: support non-4K Merkle tree block size
- [PATCH 04/10] common/verity: add _filter_fsverity_digest()
- [PATCH 01/10] common/verity: add and use _fsv_can_enable()
- [PATCH 00/10] xfstests: update verity tests for non-4K block and page size
- [PATCH 07/10] generic/577: support non-4K Merkle tree block size
- [PATCH 10/10] generic/575: test 1K Merkle tree block size
- [PATCH 09/10] generic/624: test multiple Merkle tree block sizes
- [PATCH 06/10] generic/573: support non-4K Merkle tree block size
- [PATCH 02/10] common/verity: set FSV_BLOCK_SIZE to an appropriate value
- Re: [PATCH] fsverity: mark builtin signatures as deprecated
- Re: [PATCH 0/7] ext4 fast-commit fixes
- Re: [PATCH] fsverity: mark builtin signatures as deprecated
- Re: [PATCH] fsverity: mark builtin signatures as deprecated
- Re: [PATCH] fsverity: don't check builtin signatures when require_signatures=0
- Re: [PATCH] fsverity: mark builtin signatures as deprecated
- Re: [PATCH] fsverity: mark builtin signatures as deprecated
- Re: [PATCH] ext4: don't allow journal inode to have encrypt flag
- [PATCH] fsverity: mark builtin signatures as deprecated
- [PATCH] fsverity: don't check builtin signatures when require_signatures=0
- Re: [PATCH 0/7] ext4 fast-commit fixes
- Re: [PATCH] ext4: don't allow journal inode to have encrypt flag
- Re: [PATCH] fscrypt: add additional documentation for SM4 support
- Re: [PATCH v4 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
- Re: [PATCH] ceph: make sure all the files successfully put before unmounting
- Re: [PATCH] ceph: make sure all the files successfully put before unmounting
- [PATCH] fscrypt: remove unused Speck definitions
- Re: [PATCH] ceph: make sure all the files successfully put before unmounting
- Re: [PATCH] ceph: make sure all the files successfully put before unmounting
- Re: Feature proposal: support file content integrity verification based on fs-verity
- Re: [PATCH] ceph: make sure all the files successfully put before unmounting
- Re: [PATCH v4 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
- Re: [PATCH] ceph: make sure all the files successfully put before unmounting
- [PATCH] fscrypt: add additional documentation for SM4 support
- Re: [PATCH] ceph: make sure all the files successfully put before unmounting
- Re: [PATCH] ceph: make sure all the files successfully put before unmounting
- [PATCH v4 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- [PATCH v4 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
- [PATCH v4 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
- Re: [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- Re: Feature proposal: support file content integrity verification based on fs-verity
- [PATCH] ceph: make sure all the files successfully put before unmounting
- Re: [PATCH v4] fsverity: stop using PG_error to track error status
- Re: [PATCH] fsverity: simplify fsverity_get_digest()
- Re: [PATCH v4] fsverity: stop using PG_error to track error status
- [PATCH v5] fsverity: stop using PG_error to track error status
- Re: [PATCH v4] fsverity: stop using PG_error to track error status
- Re: [PATCH] fsverity: simplify fsverity_get_digest()
- [PATCH] fsverity: simplify fsverity_get_digest()
- Re: Feature proposal: support file content integrity verification based on fs-verity
- Re: [PATCH] ext4: don't allow journal inode to have encrypt flag
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [PATCH v4] fsverity: stop using PG_error to track error status
- Re: [PATCH 0/7] ext4 fast-commit fixes
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- Re: [PATCH v3 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- Re: [PATCH v3] fsverity: stop using PG_error to track error status
- [PATCH] fscrypt: add comment for fscrypt_valid_enc_modes_v1()
- [PATCH v4] fsverity: stop using PG_error to track error status
- Re: [PATCH v3 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
- Re: [PATCH v3 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
- Re: [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- [PATCH v3 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
- [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- [PATCH v3 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
- Re: [f2fs-dev] [PATCH v3] fsverity: stop using PG_error to track error status
- Re: [PATCH v3] fsverity: stop using PG_error to track error status
- Re: [PATCH v3] fsverity: stop using PG_error to track error status
- Re: [PATCH v2 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [PATCH v3] fsverity: stop using PG_error to track error status
- Re: [PATCH v2 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- [PATCH v2 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- [PATCH v2 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
- [PATCH v2 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
- Re: pass a struct block_device to the blk-crypto interfaces v3
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- Feature proposal: support file content integrity verification based on fs-verity
- Re: [PATCH 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [PATCH 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- [PATCH 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
- [PATCH 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
- [PATCH 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
- Re: [PATCH 3/3] blk-crypto: move internal only declarations to blk-crypto-internal.h
- Re: [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper
- Re: [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- Re: [PATCH 0/7] ext4 fast-commit fixes
- Re: [dm-devel] [PATCH 3/3] blk-crypto: move internal only declarations to blk-crypto-internal.h
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- [PATCH 3/3] blk-crypto: move internal only declarations to blk-crypto-internal.h
- [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper
- [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
- pass a struct block_device to the blk-crypto interfaces v3
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- [RFC 2/4] fs: make fscrypt support an ext4 config option
- [RFC 4/4] fs: make fscrypt support a UBIFS config option
- [RFC 3/4] fs: make fscrypt support a f2fs config option
- [RFC 1/4] fscrypt: introduce USE_FS_ENCRYPTION
- [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
- [PATCH] fscrypt: pass super_block to fscrypt_put_master_key_activeref()
- Re: [PATCH v3] fsverity: stop using PG_error to track error status
- Re: [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
- [PATCH 6.0 125/197] fscrypt: fix keyring memory leak on mount failure
- [PATCH 6.0 124/197] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- [PATCH 5.15 100/144] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- [PATCH 5.15 101/144] fscrypt: fix keyring memory leak on mount failure
- [PATCH 5.10 080/118] fscrypt: simplify master key locking
- [PATCH 5.10 082/118] fscrypt: fix keyring memory leak on mount failure
- [PATCH 5.10 081/118] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- Re: Please apply "ext4,f2fs: fix readahead of verity data" to stable
- Re: [PATCH 3/3] blk-crypto: move __blk_crypto_cfg_supported to blk-crypto-internal.h
- Re: [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper
- Re: [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
- [PATCH 5.10] ext4,f2fs: fix readahead of verity data
- Please apply "ext4,f2fs: fix readahead of verity data" to stable
- [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper
- pass a struct block_device to the blk-crypto interfaces v2
- [PATCH 3/3] blk-crypto: move __blk_crypto_cfg_supported to blk-crypto-internal.h
- [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
- Re: [PATCH 5.10 0/3] fscrypt fixes for stable
- Re: [PATCH 5.15 0/2] fscrypt fixes for stable
- Re: [PATCH 6.0 0/2] fscrypt fixes for stable
- [PATCH 4/7] ext4: add missing validation of fast-commit record lengths
- [PATCH 5/7] ext4: fix unaligned memory access in ext4_fc_reserve_space()
- [PATCH 6/7] ext4: fix off-by-one errors in fast-commit block filling
- [PATCH 7/7] ext4: simplify fast-commit CRC calculation
- [PATCH 0/7] ext4 fast-commit fixes
- [PATCH 3/7] ext4: fix leaking uninitialized memory in fast-commit journal
- [PATCH 1/7] ext4: disable fast-commit of encrypted dir operations
- [PATCH 2/7] ext4: don't set up encryption key during jbd2 transaction
- [PATCH 5.10 3/3] fscrypt: fix keyring memory leak on mount failure
- [PATCH 5.10 1/3] fscrypt: simplify master key locking
- [PATCH 5.10 2/3] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- [PATCH 5.10 0/3] fscrypt fixes for stable
- [PATCH 5.15 1/2] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- [PATCH 5.15 2/2] fscrypt: fix keyring memory leak on mount failure
- [PATCH 5.15 0/2] fscrypt fixes for stable
- [PATCH 6.0 1/2] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- [PATCH 6.0 2/2] fscrypt: fix keyring memory leak on mount failure
- [PATCH 6.0 0/2] fscrypt fixes for stable
- [xfstests PATCH v2 0/3] Fix test bugs related to fs.verity.require_signatures
- [xfstests PATCH v2 3/3] tests: fix some tests for systems with fs.verity.require_signatures=1
- [xfstests PATCH v2 2/3] generic/577: add missing file removal before empty file test
- [xfstests PATCH v2 1/3] common/verity: fix _fsv_have_hash_algorithm() with required signatures
- Re: [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
- Re: [PATCH 2/2] blk-crypto: add a blk_crypto_cfg_supported helper
- Re: [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
- Re: [PATCH 2/2] blk-crypto: add a blk_crypto_cfg_supported helper
- [xfstests PATCH 2/3] generic/577: add missing file removal before empty file test
- [xfstests PATCH 3/3] tests: fix some tests for systems with fs.verity.require_signatures=1
- [xfstests PATCH 0/3] Fix test bugs related to fs.verity.require_signatures
- [xfstests PATCH 1/3] common/verity: fix _fsv_have_hash_algorithm() with required signatures
- [PATCH 2/2] blk-crypto: add a blk_crypto_cfg_supported helper
- [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
- pass a struct block_device to the blk-crypto interfaces
- Re: [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: [f2fs-dev] f2fs_empty_dir() can be extremely slow on malicious disk images
- Re: [e2fsprogs PATCH v2] e2fsck: don't allow journal inode to have encrypt flag
- Re: [e2fsprogs PATCH] e2fsck: don't allow journal inode to have encrypt flag
- [e2fsprogs PATCH v2] e2fsck: don't allow journal inode to have encrypt flag
- Re: [e2fsprogs PATCH] e2fsck: don't allow journal inode to have encrypt flag
- Re: f2fs_empty_dir() can be extremely slow on malicious disk images
- [PATCH v5 18/18] btrfs: allow encrypting compressed extents
- [PATCH v5 16/18] btrfs: use correct name hash for nokey names
- [PATCH v5 06/18] fscrypt: document btrfs' fscrypt quirks.
- [PATCH v5 07/18] btrfs: disable various operations on encrypted inodes
- [PATCH v5 13/18] btrfs: Add new FEATURE_INCOMPAT_ENCRYPT feature flag.
- [PATCH v5 08/18] btrfs: start using fscrypt hooks
- [PATCH v5 11/18] btrfs: store a fscrypt extent context per normal file extent
- [PATCH v5 10/18] btrfs: translate btrfs encryption flags and encrypted inode flag
- [PATCH v5 15/18] btrfs: permit searching for nokey names for removal
- [PATCH v5 14/18] btrfs: implement fscrypt ioctls
- [PATCH v5 12/18] btrfs: encrypt normal file extent data if appropriate
- [PATCH v5 09/18] btrfs: add fscrypt_context items
- [PATCH v5 17/18] btrfs: encrypt verity items
- [PATCH v5 05/18] fscrypt: extent direct key policies for extent-based encryption
- [PATCH v5 03/18] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
- [PATCH v5 04/18] fscrypt: add extent-based encryption
- [PATCH v5 02/18] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
- [PATCH v5 01/18] fscrypt: expose fscrypt_nokey_name
- [PATCH v5 00/18] btrfs: add fscrypt integration
- Re: f2fs_empty_dir() can be extremely slow on malicious disk images
- f2fs_empty_dir() can be extremely slow on malicious disk images
- [e2fsprogs PATCH] e2fsck: don't allow journal inode to have encrypt flag
- [PATCH] ext4: don't allow journal inode to have encrypt flag
- Re: [PATCH v4 08/21] btrfs: setup qstrings from dentrys using fscrypt helper
- Re: INFO: task hung in fscrypt_ioctl_set_policy
- INFO: task hung in fscrypt_ioctl_set_policy
- [PATCH 1/6] fsverity: support verification with tree block size < PAGE_SIZE
- [PATCH 6/6] ext4: allow verity with fs block size < PAGE_SIZE
- [PATCH 2/6] fsverity: support enabling with tree block size < PAGE_SIZE
- [PATCH 0/6] fsverity: support for non-4K pages
- [PATCH 5/6] fs/buffer.c: support fsverity in block_read_full_folio()
- [PATCH 4/6] f2fs: simplify f2fs_readpage_limit()
- [PATCH 3/6] ext4: simplify ext4_readpage_limit()
- [PATCH v3] fsverity: stop using PG_error to track error status
- Re: [PATCH v2 2/2] fsverity: stop using PG_error to track error status
- Re: [GIT PULL] fscrypt fix for 6.1-rc3
- Re: [GIT PULL] fscrypt fix for 6.1-rc3
- Re: [GIT PULL] fscrypt fix for 6.1-rc3
- Re: [GIT PULL] fscrypt fix for 6.1-rc3
- Re: [PATCH v4 02/21] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
- [GIT PULL] fscrypt fix for 6.1-rc3
- Re: [PATCH v4 08/21] btrfs: setup qstrings from dentrys using fscrypt helper
- Re: [PATCH v4 00/21] btrfs: add fscrypt integration
- [PATCH v4 19/21] btrfs: permit searching for nokey names for removal
- [PATCH v4 14/21] btrfs: translate btrfs encryption flags and encrypted inode flag
- [PATCH v4 16/21] btrfs: encrypt normal file extent data if appropriate
- [PATCH v4 15/21] btrfs: store a fscrypt extent context per normal file extent
- [PATCH v4 21/21] btrfs: encrypt verity items
- [PATCH v4 18/21] btrfs: implement fscrypt ioctls
- [PATCH v4 09/21] btrfs: use struct fscrypt_str instead of struct qstr
- [PATCH v4 11/21] btrfs: disable various operations on encrypted inodes
- [PATCH v4 17/21] btrfs: Add new FEATURE_INCOMPAT_ENCRYPT feature flag.
- [PATCH v4 20/21] btrfs: use correct name hash for nokey names
- [PATCH v4 12/21] btrfs: start using fscrypt hooks
- [PATCH v4 13/21] btrfs: add fscrypt_context items
- [PATCH v4 10/21] btrfs: store directory encryption state
- [PATCH v4 08/21] btrfs: setup qstrings from dentrys using fscrypt helper
- [PATCH v4 07/21] btrfs: use struct qstr instead of name and namelen
- [PATCH v4 06/21] fscrypt: document btrfs' fscrypt quirks.
- [PATCH v4 05/21] fscrypt: direct key policies for extent-based encryption
- [PATCH v4 03/21] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
- [PATCH v4 02/21] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
- [PATCH v4 04/21] fscrypt: add extent-based encryption
- [PATCH v4 00/21] btrfs: add fscrypt integration
- [PATCH v4 01/21] fscrypt: expose fscrypt_nokey_name
- Re: [PATCH v3 15/22] btrfs: encrypt normal file extent data if appropriate
- Re: [PATCH v3 12/22] btrfs: add fscrypt_context items
- Re: [PATCH v3 08/22] btrfs: use struct fscrypt_str instead of struct qstr
- Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
- Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
- Re: [PATCH v3 00/22] btrfs: add fscrypt integration
- Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
- Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
- Re: [PATCH v3 05/22] fscrypt: document btrfs' fscrypt quirks.
- Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
- Re: [PATCH v3 05/22] fscrypt: document btrfs' fscrypt quirks.
- Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
- Re: [PATCH v3 00/22] btrfs: add fscrypt integration
- Re: [PATCH v3 02/22] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
- [PATCH v3 21/22] fscrypt: add flag allowing partially-encrypted directories
- [PATCH v3 16/22] btrfs: Add new FEATURE_INCOMPAT_ENCRYPT feature flag.
- [PATCH v3 17/22] btrfs: implement fscrypt ioctls
- [PATCH v3 13/22] btrfs: translate btrfs encryption flags and encrypted inode flag
- [PATCH v3 08/22] btrfs: use struct fscrypt_str instead of struct qstr
- [PATCH v3 09/22] btrfs: store directory encryption state
- [PATCH v3 10/22] btrfs: disable various operations on encrypted inodes
- [PATCH v3 22/22] btrfs: encrypt verity items
- [PATCH v3 20/22] btrfs: adapt lookup for partially encrypted directories
- [PATCH v3 19/22] btrfs: use correct name hash for nokey names
- [PATCH v3 18/22] btrfs: permit searching for nokey names for removal
- [PATCH v3 15/22] btrfs: encrypt normal file extent data if appropriate
- [PATCH v3 14/22] btrfs: store a fscrypt extent context per normal file extent
- [PATCH v3 11/22] btrfs: start using fscrypt hooks
- [PATCH v3 12/22] btrfs: add fscrypt_context items
- [PATCH v3 04/22] fscrypt: add extent-based encryption
- [PATCH v3 07/22] btrfs: setup qstrings from dentrys using fscrypt helper
- [PATCH v3 05/22] fscrypt: document btrfs' fscrypt quirks.
- [PATCH v3 03/22] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
- [PATCH v3 06/22] btrfs: use struct qstr instead of name and namelen
- [PATCH v3 02/22] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
- [PATCH v3 01/22] fscrypt: expose fscrypt_nokey_name
- [PATCH v3 00/22] btrfs: add fscrypt integration
- Re: [PATCH] fscrypt: fix keyring memory leak on mount failure
- Re: [PATCH v5 0/8] make statx() return DIO alignment information
- Re: [PATCH v5 0/8] make statx() return DIO alignment information
- Re: Please don't backport "fscrypt: stop using keyrings subsystem for fscrypt_master_key" to stable until it's ready
- Re: [PATCH v5 0/8] make statx() return DIO alignment information
- Re: [PATCH] fscrypt: fix keyring memory leak on mount failure
- Please don't backport "fscrypt: stop using keyrings subsystem for fscrypt_master_key" to stable until it's ready
- Re: [syzbot] memory leak in crypto_create_tfm_node
- Re: [syzbot] memory leak in crypto_create_tfm_node
- Re: [man-pages PATCH v4] statx.2, open.2: document STATX_DIOALIGN
- Re: [syzbot] memory leak in crypto_create_tfm_node
- Re: [syzbot] memory leak in crypto_create_tfm_node
- Re: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
- [man-pages PATCH v4] statx.2, open.2: document STATX_DIOALIGN
- [PATCH] fscrypt: fix keyring memory leak on mount failure
- Semantic newlines (was: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN)
- Re: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
- Re: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
- Re: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
- Re: [PATCH] fscrypt: fix lockdep warning
- Re: [PATCH] fscrypt: fix lockdep warning
- [PATCH] fscrypt: fix lockdep warning
- [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
- Re: [GIT PULL] fsverity updates for 6.1
- Re: [GIT PULL] fscrypt updates for 6.1
- Re: [GIT PULL] STATX_DIOALIGN for 6.1
- [GIT PULL] STATX_DIOALIGN for 6.1
- [GIT PULL] fsverity updates for 6.1
- [GIT PULL] fscrypt updates for 6.1
- [RFC PATCH v6 3/4] blk-crypto: add ioctls to create and prepare hardware-wrapped keys
- [RFC PATCH v6 2/4] blk-crypto: show supported key types in sysfs
- [RFC PATCH v6 1/4] blk-crypto: add basic hardware-wrapped key support
- [RFC PATCH v6 0/4] Support for hardware-wrapped inline encryption keys
- [RFC PATCH v6 4/4] fscrypt: add support for hardware-wrapped keys
- Re: [PATCH v3] btrfs-progs: receive: add support for fs-verity
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
- Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
- Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
- Re: [PATCH v5 0/8] make statx() return DIO alignment information
- Re: [PATCH v2 12/20] btrfs: start using fscrypt hooks.
- Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
- Re: [PATCH v2 16/20] btrfs: Add new FEATURE_INCOMPAT_FSCRYPT feature flag.
- Re: [PATCH v2 05/20] fscrypt: add extent-based encryption
- Re: [PATCH v5 0/8] make statx() return DIO alignment information
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 16/20] btrfs: Add new FEATURE_INCOMPAT_FSCRYPT feature flag.
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 15/20] btrfs: store a fscrypt extent context per normal file extent
- Re: [PATCH v2 19/20] btrfs: encrypt normal file extent data if appropriate
- Re: [PATCH v2 18/20] btrfs: adapt directory read and lookup to potentially encrypted filenames
- Re: [PATCH v2 14/20] btrfs: translate btrfs encryption flags and encrypted inode flag.
- Re: [PATCH v2 13/20] btrfs: add fscrypt_context items.
- Re: [PATCH v2 12/20] btrfs: start using fscrypt hooks.
- Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- Re: [PATCH v2 09/20] btrfs: setup fscrypt_names from dentrys using helper
- Re: [PATCH v2 07/20] btrfs: store directory's encryption state
- Re: [PATCH v2 06/20] fscrypt: document btrfs' fscrypt quirks.
- Re: [PATCH v2 05/20] fscrypt: add extent-based encryption
- Re: [PATCH v2 04/20] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
- Re: [PATCH v2 03/20] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
- Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
- Re: [PATCH v2 01/20] fscrypt: expose fscrypt_nokey_name
- Re: [PATCH v2 15/20] btrfs: store a fscrypt extent context per normal file extent
- Re: [PATCH v2 20/20] btrfs: implement fscrypt ioctls
- Re: [PATCH v2 17/20] btrfs: reuse encrypted filename hash when possible.
- Re: [PATCH v2 15/20] btrfs: store a fscrypt extent context per normal file extent
- Re: [PATCH v2 13/20] btrfs: add fscrypt_context items.
- Re: [PATCH v2 12/20] btrfs: start using fscrypt hooks.
- Re: [PATCH v2 12/20] btrfs: start using fscrypt hooks.
- Re: [PATCH v2 11/20] btrfs: disable various operations on encrypted inodes
- Re: [PATCH v2 08/20] btrfs: use fscrypt_names instead of name/len everywhere.
- Re: [PATCH v2 05/20] fscrypt: add extent-based encryption
- Re: [PATCH v2 00/20] btrfs: add fscrypt integration
- Re: [PATCH v5 1/8] statx: add direct I/O alignment information
- Re: [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices
- Re: [PATCH 1/2] fstests: fscrypt: enable btrfs testing.
- Re: [PATCH v2 00/20] btrfs: add fscrypt integration
- Re: [PATCH v2 00/20] btrfs: add fscrypt integration
- Re: [PATCH v2 00/20] btrfs: add fscrypt integration
- Re: [PATCH v2 00/20] btrfs: add fscrypt integration
- Re: [PATCH v5 0/8] make statx() return DIO alignment information
- Re: [f2fs-dev] [PATCH v2 2/2] fsverity: stop using PG_error to track error status
- Re: [f2fs-dev] [PATCH v2 1/2] fscrypt: stop using PG_error to track error status
- Re: [PATCH v5 8/8] xfs: support STATX_DIOALIGN
- Re: [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices
- [PATCH v2 16/20] btrfs: Add new FEATURE_INCOMPAT_FSCRYPT feature flag.
- [PATCH v2 11/20] btrfs: disable various operations on encrypted inodes
- [PATCH v2 14/20] btrfs: translate btrfs encryption flags and encrypted inode flag.
- [PATCH v2 17/20] btrfs: reuse encrypted filename hash when possible.
- [PATCH v2 20/20] btrfs: implement fscrypt ioctls
- [PATCH v2 18/20] btrfs: adapt directory read and lookup to potentially encrypted filenames
- [PATCH v2 19/20] btrfs: encrypt normal file extent data if appropriate
- [PATCH v2 12/20] btrfs: start using fscrypt hooks.
- [PATCH v2 15/20] btrfs: store a fscrypt extent context per normal file extent
- [PATCH v2 13/20] btrfs: add fscrypt_context items.
- [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
- [PATCH v2 07/20] btrfs: store directory's encryption state
- [PATCH v2 09/20] btrfs: setup fscrypt_names from dentrys using helper
- [PATCH v2 06/20] fscrypt: document btrfs' fscrypt quirks.
- [PATCH v2 05/20] fscrypt: add extent-based encryption
- [PATCH v2 04/20] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
- [PATCH v2 03/20] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
- [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
- [PATCH v2 01/20] fscrypt: expose fscrypt_nokey_name
- [PATCH v2 00/20] btrfs: add fscrypt integration
- [PATCH 2/2] fstests: fscrypt: update tests of encryption contents for btrfs
- [PATCH 1/2] fstests: fscrypt: enable btrfs testing.
- [PATCH 0/2] fstests: add btrfs encryption support
- [PATCH v4 1/3] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- [PATCH v4 2/3] fscrypt: stop holding extra request_queue references
- [PATCH v4 3/3] fscrypt: work on block_devices instead of request_queues
- [PATCH v4 0/3] fscrypt: rework keyring and stop using request_queue
- Re: [PATCH v5 7/8] f2fs: support STATX_DIOALIGN
- Re: [PATCH v5 5/8] f2fs: move f2fs_force_buffered_io() into file.c
- Re: [PATCH v5 6/8] f2fs: simplify f2fs_force_buffered_io()
- Re: [PATCH v5 8/8] xfs: support STATX_DIOALIGN
- Re: [PATCH v4 0/9] make statx() return DIO alignment information
- [PATCH v5 7/8] f2fs: support STATX_DIOALIGN
- [PATCH v5 5/8] f2fs: move f2fs_force_buffered_io() into file.c
- [PATCH v5 8/8] xfs: support STATX_DIOALIGN
- [PATCH v5 4/8] ext4: support STATX_DIOALIGN
- [PATCH v5 3/8] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN
- [PATCH v5 6/8] f2fs: simplify f2fs_force_buffered_io()
- [PATCH v5 0/8] make statx() return DIO alignment information
- [PATCH v5 1/8] statx: add direct I/O alignment information
- [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices
- Re: [PATCH v4 0/9] make statx() return DIO alignment information
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- Re: [PATCH v2 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity
- [PATCH v3 0/3] fscrypt: rework keyring and stop using request_queue
- [PATCH v3 1/3] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- [PATCH v3 3/3] fscrypt: work on block_devices instead of request_queues
- [PATCH v3 2/3] fscrypt: stop holding extra request_queue references
- Re: [PATCH v2 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity
- Re: [PATCH v4] btrfs: send: add support for fs-verity
- Re: [PATCH v2 0/2] fscrypt: rework filesystem-level keyring
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- [PATCH v2 2/2] fscrypt: stop holding extra request_queue references
- [PATCH v2 0/2] fscrypt: rework filesystem-level keyring
- [PATCH v2 1/2] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- Re: [PATCH 05/21] fscrypt: add new encryption policy for btrfs.
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- Re: [PATCH v4] fstests: add btrfs fs-verity send/recv test
- Re: [PATCH] fs-verity: use kmap_local_page() instead of kmap()
- From: Fabio M. De Francesco
- [PATCH v4] fstests: add btrfs fs-verity send/recv test
- Re: [PATCH] fs-verity: use kmap_local_page() instead of kmap()
- Re: [PATCH] fs-verity: use kmap_local_page() instead of kmap()
- From: Fabio M. De Francesco
- Re: [PATCH] fs-verity: use memcpy_from_page()
- From: Fabio M. De Francesco
- Re: [PATCH v3] fstests: add btrfs fs-verity send/recv test
- Re: [PATCH] fs-verity: use kmap_local_page() instead of kmap()
- From: Fabio M. De Francesco
- [PATCH 1/2] fscrypt: stop using keyrings subsystem for fscrypt_master_key
- [PATCH 0/2] fscrypt: rework filesystem-level keyring
- [PATCH 2/2] fscrypt: stop holding extra request_queue references
- Re: [PATCH 05/21] fscrypt: add new encryption policy for btrfs.
- [PATCH] fs-verity: use kmap_local_page() instead of kmap()
- [PATCH] fs-verity: use memcpy_from_page()
- Re: [PATCH v3] fstests: add btrfs fs-verity send/recv test
- [PATCH v3] fstests: add btrfs fs-verity send/recv test
- Re: [PATCH 05/21] fscrypt: add new encryption policy for btrfs.
- Re: [PATCH v2] fstests: add btrfs fs-verity send/recv test
- [PATCH v2] fstests: add btrfs fs-verity send/recv test
- Re: [PATCH] fstests: add btrfs fs-verity send/recv test
- Re: [PATCH v4] btrfs: send: add support for fs-verity
- Re: [PATCH v4] btrfs: send: add support for fs-verity
- Re: [PATCH v4] btrfs: send: add support for fs-verity
- Re: [PATCH v4] btrfs: send: add support for fs-verity
- Re: [PATCH v4] btrfs: send: add support for fs-verity
- Re: [PATCH] fstests: add btrfs fs-verity send/recv test
- Re: [PATCH v4] btrfs: send: add support for fs-verity
- Re: [PATCH 05/21] fscrypt: add new encryption policy for btrfs.
- [PATCH 20/21] btrfs: encrypt normal file extent data if appropriate
- [PATCH 21/21] btrfs: implement fscrypt ioctls
- [PATCH 08/21] btrfs: setup fscrypt_names from dentrys using helper
- [PATCH 01/21] fscrypt: expose fscrypt_nokey_name
- [PATCH 06/21] btrfs: store directorys' encryption state
- [PATCH 02/21] fscrypt: add flag allowing partially-encrypted directories
- [PATCH 17/21] btrfs: Add new FEATURE_INCOMPAT_FSCRYPT feature flag.
- [PATCH 14/21] btrfs: translate btrfs encryption flags and encrypted inode flag.
- [PATCH 18/21] btrfs: reuse encrypted filename hash when possible.
- [PATCH 03/21] fscrypt: add fscrypt_have_same_policy() to check inode's compatibility
- [PATCH 19/21] btrfs: adapt directory read and lookup to potentially encrypted filenames
- [PATCH 13/21] btrfs: add fscrypt_context items.
- [PATCH 15/21] btrfs: add iv generation function for fscrypt
- [PATCH 04/21] fscrypt: add a function for a filesystem to generate an IV
- [PATCH 12/21] btrfs: start using fscrypt hooks.
- [PATCH 10/21] btrfs: disable various operations on encrypted inodes
- [PATCH 16/21] btrfs: store an IV per encrypted normal file extent
- [PATCH 11/21] btrfs: add fscrypt operation table to superblock
- [PATCH 09/21] btrfs: factor a fscrypt_name matching method
- [PATCH 05/21] fscrypt: add new encryption policy for btrfs.
- [PATCH 00/21] btrfs: add fscrypt integration
- [PATCH 2/2] fstests: fscrypt: update tests of encryption contents for btrfs
- [PATCH 0/2] fstests: add btrfs encryption support
- [PATCH 1/2] fstests: fscrypt: enable btrfs testing.
- Re: RFC: what to do about fscrypt vs block device interaction
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- Re: [PATCH v4] btrfs: send: add support for fs-verity
- [PATCH v2 2/2] fsverity: stop using PG_error to track error status
- [PATCH v2 1/2] fscrypt: stop using PG_error to track error status
- [PATCH v2 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity
- [PATCH] fstests: add btrfs fs-verity send/recv test
- [PATCH v4] btrfs: send: add support for fs-verity
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- [PATCH v3] btrfs-progs: receive: add support for fs-verity
- Re: [PATCH v3 5/5] fscrypt: remove fscrypt_set_test_dummy_encryption()
- Re: [PATCH v6 0/2] generic: test HCTR2 filename encryption
- Re: [PATCH v6 0/2] generic: test HCTR2 filename encryption
- [PATCH v6 1/2] fscrypt-crypt-util: add HCTR2 implementation
- [PATCH v6 2/2] generic: add tests for fscrypt policies with HCTR2
- [PATCH v6 0/2] generic: test HCTR2 filename encryption
- Re: [RFC PATCH v8 07/17] ipe: add auditing support
- Re: [PATCH v5 2/2] generic: add tests for fscrypt policies with HCTR2
- Re: [PATCH v5 1/2] fscrypt-crypt-util: add HCTR2 implementation
- Re: [PATCH v3] btrfs: send: add support for fs-verity
- Re: [PATCH v3] btrfs: send: add support for fs-verity
- [PATCH v5 0/2] generic: test HCTR2 filename encryption
- [PATCH v5 2/2] generic: add tests for fscrypt policies with HCTR2
- Re: [PATCH v5 0/2] generic: test HCTR2 filename encryption
- [PATCH v5 1/2] fscrypt-crypt-util: add HCTR2 implementation
- Re: [PATCH v3] btrfs: send: add support for fs-verity
- Re: [GIT PULL] fsverity update for 5.20
- Re: [PATCH v2] btrfs-progs: receive: add support for fs-verity
- Re: [PATCH v3] btrfs: send: add support for fs-verity
- [GIT PULL] fsverity update for 5.20
- Re: [PATCH v2] btrfs: send: add support for fs-verity
- Re: [PATCH v2] btrfs-progs: receive: add support for fs-verity
- Re: [PATCH v2] btrfs: send: add support for fs-verity
- Re: [PATCH v2] btrfs: send: add support for fs-verity
- [PATCH v3] btrfs: send: add support for fs-verity
- Re: [PATCH v2] btrfs: send: add support for fs-verity
- Re: [PATCH v2] btrfs: send: add support for fs-verity
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- [PATCH v2] btrfs-progs: receive: add support for fs-verity
- [PATCH v2] btrfs: send: add support for fs-verity
- Re: [PATCH] btrfs: send: add support for fs-verity
- Re: [PATCH] btrfs: send: add support for fs-verity
- [PATCH] btrfs-progs: receive: add support for fs-verity
- [PATCH] fstests: add btrfs fs-verity send/recv test
- [PATCH] btrfs: send: add support for fs-verity
- Re: [PATCH RFC 4/4] fscrypt: Add new encryption policy for btrfs.
- Re: [PATCH RFC 4/4] fscrypt: Add new encryption policy for btrfs.
- Re: [PATCH 1/1] block: Add support for setting inline encryption key per block device
- Re: [PATCH RFC 4/4] fscrypt: Add new encryption policy for btrfs.
- Re: [PATCH RFC 2/4] fscrypt: add flag allowing partially-encrypted directories
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- Re: [PATCH RFC 4/4] fscrypt: Add new encryption policy for btrfs.
- Re: [PATCH RFC 2/4] fscrypt: add flag allowing partially-encrypted directories
- Re: [PATCH v13 2/5] common/verity: support btrfs in generic fsverity tests
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- [PATCH RFC 4/4] fscrypt: Add new encryption policy for btrfs.
- [PATCH RFC 3/4] fscrypt: add fscrypt_have_same_policy() to check inode's compatibility
- [PATCH RFC 2/4] fscrypt: add flag allowing partially-encrypted directories
- [PATCH RFC 1/4] fscrypt: expose fscrypt_nokey_name
- [PATCH RFC 0/4] fscrypt changes for btrfs encryption
- Re: RFC: what to do about fscrypt vs block device interaction
- Re: [PATCH v4 2/9] vfs: support STATX_DIOALIGN on block devices
- Re: [PATCH v4 1/9] statx: add direct I/O alignment information
- Re: [PATCH v4 4/9] ext4: support STATX_DIOALIGN
- Re: [PATCH v4 1/9] statx: add direct I/O alignment information
- Re: [man-pages RFC PATCH v2] statx.2, open.2: document STATX_DIOALIGN
- Re: [PATCH v4 9/9] xfs: support STATX_DIOALIGN
- Re: RFC: what to do about fscrypt vs block device interaction
- Re: RFC: what to do about fscrypt vs block device interaction
- Re: [dm-devel] [PATCH 1/1] block: Add support for setting inline encryption key per block device
- Re: [PATCH v4 9/9] xfs: support STATX_DIOALIGN
- Re: [PATCH v4 3/9] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN
- Re: [PATCH v4 2/9] vfs: support STATX_DIOALIGN on block devices
- [man-pages RFC PATCH v2] statx.2, open.2: document STATX_DIOALIGN
- [PATCH v4 9/9] xfs: support STATX_DIOALIGN
- [PATCH v4 3/9] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN
- [PATCH v4 7/9] f2fs: simplify f2fs_force_buffered_io()
- [PATCH v4 0/9] make statx() return DIO alignment information
- [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
- [PATCH v4 5/9] f2fs: move f2fs_force_buffered_io() into file.c
- [PATCH v4 1/9] statx: add direct I/O alignment information
- [PATCH v4 8/9] f2fs: support STATX_DIOALIGN
- [PATCH v4 2/9] vfs: support STATX_DIOALIGN on block devices
- [PATCH v4 4/9] ext4: support STATX_DIOALIGN
- RFC: what to do about fscrypt vs block device interaction
- Re: [PATCH 1/1] block: Add support for setting inline encryption key per block device
- Re: [PATCH 1/1] block: Add support for setting inline encryption key per block device
- Re: [PATCH v13 4/5] btrfs: test verity orphans with dmlogwrites
- Re: [PATCH v13 0/5] tests for btrfs fsverity
- Re: [PATCH v3 0/8] make statx() return DIO alignment information
- [PATCH v13 5/5] generic: test fs-verity EFBIG scenarios
- [PATCH v13 1/5] common/verity: require corruption functionality
- [PATCH v13 2/5] common/verity: support btrfs in generic fsverity tests
- [PATCH v13 4/5] btrfs: test verity orphans with dmlogwrites
- [PATCH v13 3/5] btrfs: test btrfs specific fsverity corruption
- [PATCH v13 0/5] tests for btrfs fsverity
- Re: [PATCH v12 0/5] tests for btrfs fsverity
- Re: [PATCH v12 4/5] btrfs: test verity orphans with dmlogwrites
- Re: [RFC PATCH v4 2/2] generic: add tests for fscrypt policies with HCTR2
- Re: [RFC PATCH v4 1/2] fscrypt-crypt-util: add HCTR2 implementation
- Re: [PATCH 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity
- Re: [PATCH v12 2/5] common/verity: support btrfs in generic fsverity tests
- [PATCH v12 2/5] common/verity: support btrfs in generic fsverity tests
- [PATCH v12 1/5] common/verity: require corruption functionality
- [PATCH v12 4/5] btrfs: test verity orphans with dmlogwrites
- [PATCH v12 5/5] generic: test fs-verity EFBIG scenarios
- [PATCH v12 3/5] btrfs: test btrfs specific fsverity corruption
- [PATCH v12 0/5] tests for btrfs fsverity
- [PATCH v11 5/5] generic: test fs-verity EFBIG scenarios
- [PATCH v11 4/5] btrfs: test verity orphans with dmlogwrites
- [PATCH v11 3/5] btrfs: test btrfs specific fsverity corruption
- [PATCH v11 2/5] common/verity: support btrfs in generic fsverity tests
- [PATCH v11 0/5] tests for btrfs fsverity
- [PATCH v11 1/5] common/verity: require corruption functionality
- Re: [PATCH v10 4/5] btrfs: test verity orphans with dmlogwrites
- Re: [PATCH v10 4/5] btrfs: test verity orphans with dmlogwrites
- Re: [PATCH v10 4/5] btrfs: test verity orphans with dmlogwrites
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[Linux Kernel]
[Fedora Users]
[Yosemite Campsites]