Filesystem Crypto

• Thread Index

• [PATCH v2 1/2] fscrypt: new helper function - fscrypt_prepare_atomic_open()
  • From: Luís Henriques
• [PATCH v2 0/2] ceph: fscrypt: fix atomic open bug for encrypted directories
  • From: Luís Henriques
• Re: [PATCH 1/2] fscrypt: new helper function - fscrypt_prepare_atomic_open()
  • From: Luís Henriques
• Re: [PATCH 1/3] fscrypt: destroy keyring after security_sb_delete()
  • From: Christian Brauner
• Re: [PATCH 2/2] ceph: switch atomic open to use new fscrypt helper
  • From: Luís Henriques
• Re: [PATCH 1/2] fscrypt: new helper function - fscrypt_prepare_atomic_open()
  • From: Luís Henriques
• Re: [PATCH 1/2] fscrypt: new helper function - fscrypt_prepare_atomic_open()
  • From: Xiubo Li
• Re: [PATCH 1/2] fscrypt: new helper function - fscrypt_prepare_atomic_open()
  • From: Eric Biggers
• Re: [PATCH 1/2] fscrypt: new helper function - fscrypt_prepare_atomic_open()
  • From: Xiubo Li
• Re: [PATCH 2/2] ceph: switch atomic open to use new fscrypt helper
  • From: Xiubo Li
• Re: [syzbot] [fscrypt?] WARNING in fscrypt_destroy_keyring
  • From: Eric Biggers
• [PATCH 3/3] fscrypt: check for NULL keyring in fscrypt_put_master_key_activeref()
  • From: Eric Biggers
• [PATCH 2/3] fscrypt: improve fscrypt_destroy_keyring() documentation
  • From: Eric Biggers
• [PATCH 1/3] fscrypt: destroy keyring after security_sb_delete()
  • From: Eric Biggers
• [PATCH 0/3] Fix crash with fscrypt + Landlock
  • From: Eric Biggers
• Re: [PATCH v2 1/4] blk-mq: release crypto keyslot before reporting I/O complete
  • From: Nathan Huckleberry
• Re: [PATCH 2/2] ceph: switch atomic open to use new fscrypt helper
  • From: Luís Henriques
• Re: [PATCH 2/2] ceph: switch atomic open to use new fscrypt helper
  • From: Eric Biggers
• Re: [PATCH 1/2] fscrypt: new helper function - fscrypt_prepare_atomic_open()
  • From: Eric Biggers
• Re: [PATCH 0/2] ceph: fscrypt: fix atomic open bug for encrypted directories
  • From: Jeff Layton
• [syzbot] [fscrypt?] WARNING in fscrypt_destroy_keyring
  • From: syzbot
• [PATCH 1/2] fscrypt: new helper function - fscrypt_prepare_atomic_open()
  • From: Luís Henriques
• [PATCH 0/2] ceph: fscrypt: fix atomic open bug for encrypted directories
  • From: Luís Henriques
• [PATCH 2/2] ceph: switch atomic open to use new fscrypt helper
  • From: Luís Henriques
• Re: [PATCH 4.19] f2fs: fix cgroup writeback accounting with fs-layer encryption
  • From: Greg KH
• Re: [RFC PATCH 1/2] fscrypt: new helper function - __fscrypt_prepare_atomic_open()
  • From: Luís Henriques
• Re: [RFC PATCH 1/2] fscrypt: new helper function - __fscrypt_prepare_atomic_open()
  • From: Eric Biggers
• [RFC PATCH 2/2] ceph: switch atomic open to use new fscrypt helper
  • From: Luís Henriques
• [RFC PATCH 1/2] fscrypt: new helper function - __fscrypt_prepare_atomic_open()
  • From: Luís Henriques
• [RFC PATCH 0/2] ceph: fscrypt: fix atomic open bug for encrypted directories
  • From: Luís Henriques
• [PATCH v2 3/4] blk-crypto: remove blk_crypto_insert_cloned_request()
  • From: Eric Biggers
• [PATCH v2 1/4] blk-mq: release crypto keyslot before reporting I/O complete
  • From: Eric Biggers
• [PATCH v2 4/4] blk-crypto: drop the NULL check from blk_crypto_put_keyslot()
  • From: Eric Biggers
• [PATCH v2 2/4] blk-crypto: make blk_crypto_evict_key() more robust
  • From: Eric Biggers
• [PATCH v2 0/4] Fix blk-crypto keyslot race condition
  • From: Eric Biggers
• Re: [PATCH 1/3] blk-mq: release crypto keyslot before reporting I/O complete
  • From: Eric Biggers
• [PATCH 4.19] f2fs: fix cgroup writeback accounting with fs-layer encryption
  • From: Eric Biggers
• Re: [PATCH] ext4: fix cgroup writeback accounting with fs-layer encryption
  • From: Theodore Ts'o
• Re: [PATCH] ext4: fix cgroup writeback accounting with fs-layer encryption
  • From: Eric Biggers
• Re: [PATCH] fs/buffer.c: use b_folio for fscrypt work
  • From: Eric Biggers
• Re: [PATCH 2/3] blk-crypto: make blk_crypto_evict_key() more robust
  • From: Nathan Huckleberry
• Re: [PATCH 2/3] blk-crypto: make blk_crypto_evict_key() more robust
  • From: Eric Biggers
• Re: [PATCH 2/3] blk-crypto: make blk_crypto_evict_key() more robust
  • From: Nathan Huckleberry
• Re: [PATCH 1/3] blk-mq: release crypto keyslot before reporting I/O complete
  • From: Nathan Huckleberry
• [PATCH 2/3] blk-crypto: make blk_crypto_evict_key() more robust
  • From: Eric Biggers
• [PATCH 3/3] blk-crypto: remove blk_crypto_insert_cloned_request()
  • From: Eric Biggers
• [PATCH 1/3] blk-mq: release crypto keyslot before reporting I/O complete
  • From: Eric Biggers
• [PATCH 0/3] Fix blk-crypto keyslot race condition
  • From: Eric Biggers
• Re: [PATCH] blk-crypto: make blk_crypto_evict_key() always try to evict
  • From: Eric Biggers
• Re: [PATCH] blk-crypto: make blk_crypto_evict_key() always try to evict
  • From: Nathan Huckleberry
• Re: [RFC PATCH v9 11/16] ipe: add support for dm-verity as a trust provider
  • From: Paul Moore
• Re: [RFC PATCH v9 09/16] block|security: add LSM blob to block_device
  • From: Paul Moore
• Re: [RFC PATCH v9 08/16] ipe: add permissive toggle
  • From: Paul Moore
• Re: [RFC PATCH v9 07/16] uapi|audit|ipe: add ipe auditing support
  • From: Paul Moore
• Re: [RFC PATCH v9 06/16] ipe: add LSM hooks on execution and kernel read
  • From: Paul Moore
• Re: [RFC PATCH v9 05/16] ipe: add userspace interface
  • From: Paul Moore
• Re: [RFC PATCH v9 03/16] ipe: add evaluation loop and introduce 'boot_verified' as a trust provider
  • From: Paul Moore
• Re: [RFC PATCH v9 02/16] ipe: add policy parser
  • From: Paul Moore
• Re: [RFC PATCH v9 01/16] security: add ipe lsm
  • From: Paul Moore
• Re: [RFC PATCH v9 03/16] ipe: add evaluation loop and introduce 'boot_verified' as a trust provider
  • From: Paul Moore
• Re: [syzbot] [fscrypt?] possible deadlock in fscrypt_initialize (2)
  • From: Eric Biggers
• [syzbot] [fscrypt?] possible deadlock in fscrypt_initialize (2)
  • From: syzbot
• Re: [syzbot] [ext4?] possible deadlock in start_this_handle (4)
  • From: Eric Biggers
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Jaegeuk Kim
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Eric Biggers
• Re: [f2fs-dev] [PATCH] MAINTAINERS: update fscrypt git repo
  • From: patchwork-bot+f2fs
• Re: [f2fs-dev] [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: patchwork-bot+f2fs
• Re: [f2fs-dev] [PATCH] MAINTAINERS: update fsverity git repo, list, and patchwork
  • From: patchwork-bot+f2fs
• Re: [f2fs-dev] [PATCH 0/5] Add the test_dummy_encryption key on-demand
  • From: patchwork-bot+f2fs
• [PATCH] blk-crypto: make blk_crypto_evict_key() always try to evict
  • From: Eric Biggers
• [PATCH] fs/buffer.c: use b_folio for fscrypt work
  • From: Eric Biggers
• Re: [RFC PATCH 00/17] fscrypt: add per-extent encryption keys
  • From: Eric Biggers
• Re: [RFC PATCH 00/17] fscrypt: add per-extent encryption keys
  • From: Sweet Tea Dorminy
• Re: [RFC PATCH 00/17] fscrypt: add per-extent encryption keys
  • From: Neal Gompa
• Re: [GIT PULL] fscrypt updates for 6.3
  • From: pr-tracker-bot
• Re: [GIT PULL] fsverity updates for 6.3
  • From: pr-tracker-bot
• [GIT PULL] fsverity updates for 6.3
  • From: Eric Biggers
• [GIT PULL] fscrypt updates for 6.3
  • From: Eric Biggers
• Re: Backup/restore of fscrypt files and directories
  • From: Andreas Dilger
• Re: [RFC PATCH v9 03/16] ipe: add evaluation loop and introduce 'boot_verified' as a trust provider
  • From: Fan Wu
• Re: Backup/restore of fscrypt files and directories
  • From: Theodore Ts'o
• Re: Backup/restore of fscrypt files and directories
  • From: Sebastien Buisson
• Re: [RFC PATCH v9 06/16] ipe: add LSM hooks on execution and kernel read
  • From: Fan Wu
• Re: [RFC PATCH v9 12/16] fsverity: consume builtin signature via LSM hook
  • From: Fan Wu
• Re: [RFC PATCH v9 12/16] fsverity: consume builtin signature via LSM hook
  • From: Eric Biggers
• Re: Backup/restore of fscrypt files and directories
  • From: Eric Biggers
• Re: [PATCH 0/5] Add the test_dummy_encryption key on-demand
  • From: Linus Torvalds
• Backup/restore of fscrypt files and directories
  • From: Sebastien Buisson
• [PATCH 2/5] ext4: stop calling fscrypt_add_test_dummy_key()
  • From: Eric Biggers
• [PATCH 1/5] fscrypt: add the test dummy encryption key on-demand
  • From: Eric Biggers
• [PATCH 3/5] f2fs: stop calling fscrypt_add_test_dummy_key()
  • From: Eric Biggers
• [PATCH 5/5] fscrypt: clean up fscrypt_add_test_dummy_key()
  • From: Eric Biggers
• [PATCH 4/5] fs/super.c: stop calling fscrypt_destroy_keyring() from __put_super()
  • From: Eric Biggers
• [PATCH 0/5] Add the test_dummy_encryption key on-demand
  • From: Eric Biggers
• Re: [RFC PATCH v9 00/16] Integrity Policy Enforcement LSM (IPE)
  • From: Fan Wu
• Re: [RFC PATCH v9 13/16] ipe: enable support for fs-verity as a trust provider
  • From: Fan Wu
• Re: [RFC PATCH v9 10/16] dm-verity: consume root hash digest and signature data via LSM hook
  • From: Fan Wu
• Re: [f2fs-dev] [PATCH] f2fs: fix cgroup writeback accounting with fs-layer encryption
  • From: patchwork-bot+f2fs
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Eric Biggers
• Re: [PATCH] fscrypt: support decrypting data from large folios
  • From: Eric Biggers
• Re: [PATCH] f2fs: fix cgroup writeback accounting with fs-layer encryption
  • From: Tejun Heo
• Re: [PATCH] ext4: fix cgroup writeback accounting with fs-layer encryption
  • From: Tejun Heo
• Re: [f2fs-dev] [PATCH] f2fs: fix cgroup writeback accounting with fs-layer encryption
  • From: Chao Yu
• Re: [PATCH] fscrypt: Copy the memcg information to the ciphertext page
  • From: Eric Biggers
• [PATCH] f2fs: fix cgroup writeback accounting with fs-layer encryption
  • From: Eric Biggers
• [PATCH] ext4: fix cgroup writeback accounting with fs-layer encryption
  • From: Eric Biggers
• Re: [PATCH] fscrypt: Copy the memcg information to the ciphertext page
  • From: Tejun Heo
• Re: [RFC PATCH v9 00/16] Integrity Policy Enforcement LSM (IPE)
  • From: Roberto Sassu
• Re: [RFC PATCH v9 13/16] ipe: enable support for fs-verity as a trust provider
  • From: Roberto Sassu
• Re: [RFC PATCH v9 10/16] dm-verity: consume root hash digest and signature data via LSM hook
  • From: Roberto Sassu
• Re: [RFC PATCH v9 16/16] documentation: add ipe documentation
  • From: Fan Wu
• Re: [RFC PATCH v9 13/16] ipe: enable support for fs-verity as a trust provider
  • From: Fan Wu
• Re: [RFC PATCH v9 10/16] dm-verity: consume root hash digest and signature data via LSM hook
  • From: Fan Wu
• Re: [RFC PATCH v9 02/16] ipe: add policy parser
  • From: Fan Wu
• Re: [RFC PATCH v9 05/16] ipe: add userspace interface
  • From: Fan Wu
• Re: [PATCH] fscrypt: Copy the memcg information to the ciphertext page
  • From: Eric Biggers
• Re: [RFC PATCH v9 00/16] Integrity Policy Enforcement LSM (IPE)
  • From: Fan Wu
• Re: [RFC PATCH v9 09/16] block|security: add LSM blob to block_device
  • From: Fan Wu
• Re: [PATCH] fscrypt: Copy the memcg information to the ciphertext page
  • From: Tejun Heo
• Re: [RFC PATCH v9 07/16] uapi|audit|ipe: add ipe auditing support
  • From: Steve Grubb
• Re: [RFC PATCH v9 03/16] ipe: add evaluation loop and introduce 'boot_verified' as a trust provider
  • From: Roberto Sassu
• Re: [RFC PATCH v9 00/16] Integrity Policy Enforcement LSM (IPE)
  • From: Roberto Sassu
• Re: [RFC PATCH v9 13/16] ipe: enable support for fs-verity as a trust provider
  • From: Roberto Sassu
• Re: [RFC PATCH v9 10/16] dm-verity: consume root hash digest and signature data via LSM hook
  • From: Roberto Sassu
• Re: [RFC PATCH v9 07/16] uapi|audit|ipe: add ipe auditing support
  • From: Roberto Sassu
• Re: [RFC PATCH v9 06/16] ipe: add LSM hooks on execution and kernel read
  • From: Roberto Sassu
• Re: [RFC PATCH v9 03/16] ipe: add evaluation loop and introduce 'boot_verified' as a trust provider
  • From: Roberto Sassu
• Re: [RFC PATCH v9 02/16] ipe: add policy parser
  • From: Roberto Sassu
• Re: [RFC PATCH v9 05/16] ipe: add userspace interface
  • From: Roberto Sassu
• Re: [RFC PATCH v9 09/16] block|security: add LSM blob to block_device
  • From: Christoph Hellwig
• Re: [RFC PATCH v9 16/16] documentation: add ipe documentation
  • From: Bagas Sanjaya
• [RFC PATCH v9 03/16] ipe: add evaluation loop and introduce 'boot_verified' as a trust provider
  • From: Fan Wu
• [RFC PATCH v9 10/16] dm-verity: consume root hash digest and signature data via LSM hook
  • From: Fan Wu
• [RFC PATCH v9 06/16] ipe: add LSM hooks on execution and kernel read
  • From: Fan Wu
• [RFC PATCH v9 12/16] fsverity: consume builtin signature via LSM hook
  • From: Fan Wu
• [RFC PATCH v9 08/16] ipe: add permissive toggle
  • From: Fan Wu
• [RFC PATCH v9 05/16] ipe: add userspace interface
  • From: Fan Wu
• [RFC PATCH v9 07/16] uapi|audit|ipe: add ipe auditing support
  • From: Fan Wu
• [RFC PATCH v9 11/16] ipe: add support for dm-verity as a trust provider
  • From: Fan Wu
• [RFC PATCH v9 16/16] documentation: add ipe documentation
  • From: Fan Wu
• [RFC PATCH v9 09/16] block|security: add LSM blob to block_device
  • From: Fan Wu
• [RFC PATCH v9 13/16] ipe: enable support for fs-verity as a trust provider
  • From: Fan Wu
• [RFC PATCH v9 02/16] ipe: add policy parser
  • From: Fan Wu
• [RFC PATCH v9 15/16] ipe: kunit test for parser
  • From: Fan Wu
• [RFC PATCH v9 14/16] scripts: add boot policy generation program
  • From: Fan Wu
• [RFC PATCH v9 00/16] Integrity Policy Enforcement LSM (IPE)
  • From: Fan Wu
• [RFC PATCH v9 04/16] security: add new securityfs delete function
  • From: Fan Wu
• [RFC PATCH v9 01/16] security: add ipe lsm
  • From: Fan Wu
• Re: [PATCH] fscrypt: Copy the memcg information to the ciphertext page
  • From: Matthew Wilcox
• Re: [PATCH] fscrypt: Copy the memcg information to the ciphertext page
  • From: Eric Biggers
• [PATCH] fscrypt: Copy the memcg information to the ciphertext page
  • From: Matthew Wilcox (Oracle)
• Re: [PATCH] fscrypt: support decrypting data from large folios
  • From: Eric Biggers
• Re: [PATCH] fscrypt: support decrypting data from large folios
  • From: Matthew Wilcox
• [PATCH] fscrypt: support decrypting data from large folios
  • From: Eric Biggers
• [ANNOUNCE] Moving the fsverity-utils git repo
  • From: Eric Biggers
• Re: [PATCH 4/4] fsverity: pass pos and size to ->write_merkle_tree_block
  • From: Eric Biggers
• Re: Please update fscrypt and fsverity branches in linux-next
  • From: Stephen Rothwell
• [ANNOUNCE] New mailing list for fsverity development
  • From: Eric Biggers
• Please update fscrypt and fsverity branches in linux-next
  • From: Eric Biggers
• Re: [GIT PULL] fscrypt MAINTAINERS entry update for 6.2-rc6
  • From: pr-tracker-bot
• Re: [GIT PULL] fsverity MAINTAINERS entry update for 6.2-rc6
  • From: pr-tracker-bot
• [GIT PULL] fscrypt MAINTAINERS entry update for 6.2-rc6
  • From: Eric Biggers
• [GIT PULL] fsverity MAINTAINERS entry update for 6.2-rc6
  • From: Eric Biggers
• Re: [PATCH v2 10/11] fs/buffer.c: support fsverity in block_read_full_folio()
  • From: Christoph Hellwig
• Re: [PATCH v2 10/11] fs/buffer.c: support fsverity in block_read_full_folio()
  • From: Eric Biggers
• Re: [e2fsprogs PATCH v2] e2fsck: don't allow journal inode to have encrypt flag
  • From: Theodore Ts'o
• [linux-next:master] BUILD REGRESSION f3381a7baf5ccbd091eb2c4fd2afd84266fcef24
  • From: kernel test robot
• Re: [PATCH v3] generic/692: generalize the test for non-4K Merkle tree block sizes
  • From: Zorro Lang
• [PATCH] MAINTAINERS: update fscrypt git repo
  • From: Eric Biggers
• [PATCH] MAINTAINERS: update fsverity git repo, list, and patchwork
  • From: Eric Biggers
• Re: [PATCH v3] generic/692: generalize the test for non-4K Merkle tree block sizes
  • From: Ojaswin Mujoo
• [PATCH v3] generic/692: generalize the test for non-4K Merkle tree block sizes
  • From: Eric Biggers
• Re: [PATCH v2] generic/692: generalize the test for non-4K Merkle tree block sizes
  • From: Eric Biggers
• [PATCH v2] generic/692: generalize the test for non-4K Merkle tree block sizes
  • From: Eric Biggers
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Eric Biggers
• Re: [PATCH v2 10/11] fs/buffer.c: support fsverity in block_read_full_folio()
  • From: Eric Biggers
• Re: [PATCH v2 10/11] fs/buffer.c: support fsverity in block_read_full_folio()
  • From: Andrew Morton
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Andrey Albershteyn
• Re: [e2fsprogs PATCH v2] e2fsck: don't allow journal inode to have encrypt flag
  • From: Eric Biggers
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Eric Biggers
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Ojaswin Mujoo
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Eric Biggers
• Re: [PATCH] fsverity: remove debug messages and CONFIG_FS_VERITY_DEBUG
  • From: Eric Biggers
• Re: [PATCH 0/4] fsverity cleanups
  • From: Eric Biggers
• Re: [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Ojaswin Mujoo
• Re: Separate mailing list (and git and patchwork) for fsverity?
  • From: Eric Biggers
• Re: [RFC PATCH 15/17] fscrypt: allow load/save of extent contexts
  • From: Sweet Tea Dorminy
• Re: [RFC PATCH 15/17] fscrypt: allow load/save of extent contexts
  • From: Eric Biggers
• Re: [RFC PATCH 15/17] fscrypt: allow load/save of extent contexts
  • From: Sweet Tea Dorminy
• Re: [RFC PATCH 15/17] fscrypt: allow load/save of extent contexts
  • From: Eric Biggers
• Re: [RFC PATCH 15/17] fscrypt: allow load/save of extent contexts
  • From: Sweet Tea Dorminy
• Re: [RFC PATCH 15/17] fscrypt: allow load/save of extent contexts
  • From: Eric Biggers
• Re: [RFC PATCH 01/17] fscrypt: factor accessing inode->i_crypt_info
  • From: Eric Biggers
• Re: [PATCH v3 00/10] xfstests: update verity tests for non-4K block and page size
  • From: Zorro Lang
• [RFC PATCH 13/17] fscrypt: use an optional ino equivalent for per-extent infos
  • From: Sweet Tea Dorminy
• [RFC PATCH 01/17] fscrypt: factor accessing inode->i_crypt_info
  • From: Sweet Tea Dorminy
• [RFC PATCH 15/17] fscrypt: allow load/save of extent contexts
  • From: Sweet Tea Dorminy
• [RFC PATCH 05/17] fscrypt: use parent dir's info for extent-based encryption.
  • From: Sweet Tea Dorminy
• [RFC PATCH 09/17] fscrypt: make fscrypt_setup_encryption_info generic for extents
  • From: Sweet Tea Dorminy
• [RFC PATCH 03/17] fscrypt: adjust effective lblks based on extents
  • From: Sweet Tea Dorminy
• [RFC PATCH 08/17] fscrypt: rename mk->mk_decrypted_inodes*
  • From: Sweet Tea Dorminy
• [RFC PATCH 00/17] fscrypt: add per-extent encryption keys
  • From: Sweet Tea Dorminy
• [RFC PATCH 04/17] fscrypt: factor out fscrypt_set_inode_info()
  • From: Sweet Tea Dorminy
• [RFC PATCH 11/17] fscrypt: update all the *per_file_* function names
  • From: Sweet Tea Dorminy
• [RFC PATCH 14/17] fscrypt: add creation/usage/freeing of per-extent infos
  • From: Sweet Tea Dorminy
• [RFC PATCH 17/17] fscrypt: update documentation to mention per-extent keys.
  • From: Sweet Tea Dorminy
• [RFC PATCH 02/17] fscrypt: separate getting info for a specific block
  • From: Sweet Tea Dorminy
• [RFC PATCH 06/17] fscrypt: add a super_block pointer to fscrypt_info
  • From: Sweet Tea Dorminy
• [RFC PATCH 12/17] fscrypt: notify per-extent infos if master key vanishes
  • From: Sweet Tea Dorminy
• [RFC PATCH 10/17] fscrypt: let fscrypt_infos be owned by an extent
  • From: Sweet Tea Dorminy
• [RFC PATCH 07/17] fscrypt: update comments about inodes to include extents
  • From: Sweet Tea Dorminy
• [RFC PATCH 16/17] fscrypt: disable inline encryption for extent-based encryption
  • From: Sweet Tea Dorminy
• Re: [RFC] fs-verity and encryption for EROFS
  • From: Gao Xiang
• Re: [RFC] fs-verity and encryption for EROFS
  • From: Eric Biggers
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Xiubo Li
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Eric Biggers
• Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
  • From: Eric Biggers
• [PATCH v3 03/10] common/verity: use FSV_BLOCK_SIZE by default
  • From: Eric Biggers
• [PATCH v3 01/10] common/verity: add and use _fsv_can_enable()
  • From: Eric Biggers
• [PATCH v3 08/10] generic/574: test multiple Merkle tree block sizes
  • From: Eric Biggers
• [PATCH v3 02/10] common/verity: set FSV_BLOCK_SIZE to an appropriate value
  • From: Eric Biggers
• [PATCH v3 10/10] generic/575: test 1K Merkle tree block size
  • From: Eric Biggers
• [PATCH v3 04/10] common/verity: add _filter_fsverity_digest()
  • From: Eric Biggers
• [PATCH v3 09/10] generic/624: test multiple Merkle tree block sizes
  • From: Eric Biggers
• [PATCH v3 07/10] generic/577: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH v3 05/10] generic/572: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH v3 06/10] generic/573: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH v3 00/10] xfstests: update verity tests for non-4K block and page size
  • From: Eric Biggers
• Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
  • From: Zorro Lang
• Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
  • From: Theodore Ts'o
• Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
  • From: Eric Biggers
• Re: [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
  • From: Zorro Lang
• [PATCH v2 07/11] fsverity: support enabling with tree block size < PAGE_SIZE
  • From: Eric Biggers
• [PATCH v2 03/11] fsverity: store log2(digest_size) precomputed
  • From: Eric Biggers
• [PATCH v2 10/11] fs/buffer.c: support fsverity in block_read_full_folio()
  • From: Eric Biggers
• [PATCH v2 11/11] ext4: allow verity with fs block size < PAGE_SIZE
  • From: Eric Biggers
• [PATCH v2 04/11] fsverity: use EFBIG for file too large to enable verity
  • From: Eric Biggers
• [PATCH v2 08/11] ext4: simplify ext4_readpage_limit()
  • From: Eric Biggers
• [PATCH v2 09/11] f2fs: simplify f2fs_readpage_limit()
  • From: Eric Biggers
• [PATCH v2 06/11] fsverity: support verification with tree block size < PAGE_SIZE
  • From: Eric Biggers
• [PATCH v2 05/11] fsverity: replace fsverity_hash_page() with fsverity_hash_block()
  • From: Eric Biggers
• [PATCH v2 02/11] fsverity: simplify Merkle tree readahead size calculation
  • From: Eric Biggers
• [PATCH v2 00/11] fsverity: support for non-4K pages
  • From: Eric Biggers
• [PATCH v2 01/11] fsverity: use unsigned long for level_start
  • From: Eric Biggers
• [PATCH v2 05/10] generic/572: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes
  • From: Eric Biggers
• [PATCH v2 04/10] common/verity: add _filter_fsverity_digest()
  • From: Eric Biggers
• [PATCH v2 03/10] common/verity: use FSV_BLOCK_SIZE by default
  • From: Eric Biggers
• [PATCH v2 10/10] generic/575: test 1K Merkle tree block size
  • From: Eric Biggers
• [PATCH v2 09/10] generic/624: test multiple Merkle tree block sizes
  • From: Eric Biggers
• [PATCH v2 07/10] generic/577: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH v2 02/10] common/verity: set FSV_BLOCK_SIZE to an appropriate value
  • From: Eric Biggers
• [PATCH v2 01/10] common/verity: add and use _fsv_can_enable()
  • From: Eric Biggers
• [PATCH v2 06/10] generic/573: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH v2 00/10] xfstests: update verity tests for non-4K block and page size
  • From: Eric Biggers
• Re: Separate mailing list (and git and patchwork) for fsverity?
  • From: Theodore Ts'o
• Re: [RFC] fs-verity and encryption for EROFS
  • From: Gao Xiang
• Re: Separate mailing list (and git and patchwork) for fsverity?
  • From: Eric Biggers
• [RFC] fs-verity and encryption for EROFS
  • From: Gao Xiang
• Re: [PATCH 09/10] generic/624: test multiple Merkle tree block sizes
  • From: Zorro Lang
• Re: [PATCH 09/10] generic/624: test multiple Merkle tree block sizes
  • From: Eric Biggers
• Re: [PATCH 09/10] generic/624: test multiple Merkle tree block sizes
  • From: Zorro Lang
• Re: [PATCH] fsverity: don't check builtin signatures when require_signatures=0
  • From: Eric Biggers
• Re: [PATCH] fsverity: don't check builtin signatures when require_signatures=0
  • From: Luca Boccassi
• Re: [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Luca Boccassi
• Re: [PATCH] fsverity: don't check builtin signatures when require_signatures=0
  • From: Eric Biggers
• Re: [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Eric Biggers
• Re: [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Eric Biggers
• [RFC PATCH v7 2/4] blk-crypto: show supported key types in sysfs
  • From: Eric Biggers
• [RFC PATCH v7 1/4] blk-crypto: add basic hardware-wrapped key support
  • From: Eric Biggers
• [RFC PATCH v7 4/4] fscrypt: add support for hardware-wrapped keys
  • From: Eric Biggers
• [RFC PATCH v7 3/4] blk-crypto: add ioctls to create and prepare hardware-wrapped keys
  • From: Eric Biggers
• [RFC PATCH v7 0/4] Support for hardware-wrapped inline encryption keys
  • From: Eric Biggers
• [PATCH] fsverity: remove debug messages and CONFIG_FS_VERITY_DEBUG
  • From: Eric Biggers
• Re: [PATCH 0/4] fsverity cleanups
  • From: Dave Chinner
• [PATCH 2/4] fsverity: optimize fsverity_prepare_setattr() on non-verity files
  • From: Eric Biggers
• [PATCH 4/4] fsverity: pass pos and size to ->write_merkle_tree_block
  • From: Eric Biggers
• [PATCH 3/4] fsverity: optimize fsverity_cleanup_inode() on non-verity files
  • From: Eric Biggers
• [PATCH 0/4] fsverity cleanups
  • From: Eric Biggers
• [PATCH 1/4] fsverity: optimize fsverity_file_open() on non-verity files
  • From: Eric Biggers
• Re: [PATCH] fscrypt: Fix null pointer when defer i_crypt_info
  • From: Eric Biggers
• Re: [PATCH] fscrypt: Fix null pointer when defer i_crypt_info
  • From: Jun Nie
• Separate mailing list (and git and patchwork) for fsverity?
  • From: Eric Biggers
• Re: [PATCH] fscrypt: Fix null pointer when defer i_crypt_info
  • From: Eric Biggers
• [PATCH] fscrypt: Fix null pointer when defer i_crypt_info
  • From: Jun Nie
• Re: [GIT PULL] fsverity updates for 6.2
  • From: pr-tracker-bot
• Re: [GIT PULL] fscrypt updates for 6.2
  • From: pr-tracker-bot
• [GIT PULL] fsverity updates for 6.2
  • From: Eric Biggers
• [GIT PULL] fscrypt updates for 6.2
  • From: Eric Biggers
• [PATCH 08/10] generic/574: test multiple Merkle tree block sizes
  • From: Eric Biggers
• [PATCH 03/10] common/verity: use FSV_BLOCK_SIZE by default
  • From: Eric Biggers
• [PATCH 05/10] generic/572: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH 04/10] common/verity: add _filter_fsverity_digest()
  • From: Eric Biggers
• [PATCH 01/10] common/verity: add and use _fsv_can_enable()
  • From: Eric Biggers
• [PATCH 00/10] xfstests: update verity tests for non-4K block and page size
  • From: Eric Biggers
• [PATCH 07/10] generic/577: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH 10/10] generic/575: test 1K Merkle tree block size
  • From: Eric Biggers
• [PATCH 09/10] generic/624: test multiple Merkle tree block sizes
  • From: Eric Biggers
• [PATCH 06/10] generic/573: support non-4K Merkle tree block size
  • From: Eric Biggers
• [PATCH 02/10] common/verity: set FSV_BLOCK_SIZE to an appropriate value
  • From: Eric Biggers
• Re: [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Fan Wu
• Re: [PATCH 0/7] ext4 fast-commit fixes
  • From: harshad shirwadkar
• Re: [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Luca Boccassi
• Re: [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Eric Biggers
• Re: [PATCH] fsverity: don't check builtin signatures when require_signatures=0
  • From: Luca Boccassi
• Re: [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Paul Moore
• Re: [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Luca Boccassi
• Re: [PATCH] ext4: don't allow journal inode to have encrypt flag
  • From: Eric Biggers
• [PATCH] fsverity: mark builtin signatures as deprecated
  • From: Eric Biggers
• [PATCH] fsverity: don't check builtin signatures when require_signatures=0
  • From: Eric Biggers
• Re: [PATCH 0/7] ext4 fast-commit fixes
  • From: Theodore Ts'o
• Re: [PATCH] ext4: don't allow journal inode to have encrypt flag
  • From: Theodore Ts'o
• Re: [PATCH] fscrypt: add additional documentation for SM4 support
  • From: Tianjia Zhang
• Re: [PATCH v4 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
  • From: Tianjia Zhang
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Xiubo Li
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Eric Biggers
• [PATCH] fscrypt: remove unused Speck definitions
  • From: Eric Biggers
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Xiubo Li
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Xiubo Li
• Re: Feature proposal: support file content integrity verification based on fs-verity
  • From: Victor Hsieh
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Eric Biggers
• Re: [PATCH v4 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
  • From: Eric Biggers
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Eric Biggers
• [PATCH] fscrypt: add additional documentation for SM4 support
  • From: Eric Biggers
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Xiubo Li
• Re: [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: Ilya Dryomov
• [PATCH v4 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Tianjia Zhang
• [PATCH v4 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
  • From: Tianjia Zhang
• [PATCH v4 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
  • From: Tianjia Zhang
• Re: [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Tianjia Zhang
• Re: Feature proposal: support file content integrity verification based on fs-verity
  • From: Gerry Liu
• [PATCH] ceph: make sure all the files successfully put before unmounting
  • From: xiubli
• Re: [PATCH v4] fsverity: stop using PG_error to track error status
  • From: Jaegeuk Kim
• Re: [PATCH] fsverity: simplify fsverity_get_digest()
  • From: Mimi Zohar
• Re: [PATCH v4] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• [PATCH v5] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• Re: [PATCH v4] fsverity: stop using PG_error to track error status
  • From: Jaegeuk Kim
• Re: [PATCH] fsverity: simplify fsverity_get_digest()
  • From: Eric Biggers
• [PATCH] fsverity: simplify fsverity_get_digest()
  • From: Eric Biggers
• Re: Feature proposal: support file content integrity verification based on fs-verity
  • From: Victor Hsieh
• Re: [PATCH] ext4: don't allow journal inode to have encrypt flag
  • From: Eric Biggers
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Paul Crowley
• Re: [PATCH v4] fsverity: stop using PG_error to track error status
  • From: Jaegeuk Kim
• Re: [PATCH 0/7] ext4 fast-commit fixes
  • From: Eric Biggers
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Eric Biggers
• Re: [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Bagas Sanjaya
• Re: [PATCH v3 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
  • From: Bagas Sanjaya
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Christoph Hellwig
• Re: [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Tianjia Zhang
• Re: [PATCH v3] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• [PATCH] fscrypt: add comment for fscrypt_valid_enc_modes_v1()
  • From: Eric Biggers
• [PATCH v4] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• Re: [PATCH v3 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
  • From: Jens Axboe
• Re: [PATCH v3 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
  • From: Eric Biggers
• Re: [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Eric Biggers
• [PATCH v3 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
  • From: Tianjia Zhang
• [PATCH v3 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Tianjia Zhang
• [PATCH v3 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
  • From: Tianjia Zhang
• Re: [f2fs-dev] [PATCH v3] fsverity: stop using PG_error to track error status
  • From: Chao Yu
• Re: [PATCH v3] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• Re: [PATCH v3] fsverity: stop using PG_error to track error status
  • From: Chao Yu
• Re: [PATCH v2 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Tianjia Zhang
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Sweet Tea Dorminy
• Re: [PATCH v3] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• Re: [PATCH v2 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Eric Biggers
• [PATCH v2 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Tianjia Zhang
• [PATCH v2 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
  • From: Tianjia Zhang
• [PATCH v2 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
  • From: Tianjia Zhang
• Re: pass a struct block_device to the blk-crypto interfaces v3
  • From: Jens Axboe
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Sweet Tea Dorminy
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Niels de Vos
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Niels de Vos
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Niels de Vos
• Feature proposal: support file content integrity verification based on fs-verity
  • From: Gmail
• Re: [PATCH 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Tianjia Zhang
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Eric Biggers
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Sweet Tea Dorminy
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Neal Gompa
• Re: [PATCH 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Eric Biggers
• [PATCH 0/2] Add SM4 XTS symmetric algorithm for blk-crypto and fscrypt
  • From: Tianjia Zhang
• [PATCH 2/2] fscrypt: Add SM4 XTS/CTS symmetric algorithm support
  • From: Tianjia Zhang
• [PATCH 1/2] blk-crypto: Add support for SM4-XTS blk crypto mode
  • From: Tianjia Zhang
• Re: [PATCH 3/3] blk-crypto: move internal only declarations to blk-crypto-internal.h
  • From: Eric Biggers
• Re: [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper
  • From: Eric Biggers
• Re: [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
  • From: Eric Biggers
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Eric Biggers
• Re: [PATCH 0/7] ext4 fast-commit fixes
  • From: Eric Biggers
• Re: [dm-devel] [PATCH 3/3] blk-crypto: move internal only declarations to blk-crypto-internal.h
  • From: Christoph Hellwig
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Christoph Hellwig
• [PATCH 3/3] blk-crypto: move internal only declarations to blk-crypto-internal.h
  • From: Christoph Hellwig
• [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper
  • From: Christoph Hellwig
• [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
  • From: Christoph Hellwig
• pass a struct block_device to the blk-crypto interfaces v3
  • From: Christoph Hellwig
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Theodore Ts'o
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Theodore Ts'o
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Niels de Vos
• Re: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Theodore Ts'o
• [RFC 2/4] fs: make fscrypt support an ext4 config option
  • From: Niels de Vos
• [RFC 4/4] fs: make fscrypt support a UBIFS config option
  • From: Niels de Vos
• [RFC 3/4] fs: make fscrypt support a f2fs config option
  • From: Niels de Vos
• [RFC 1/4] fscrypt: introduce USE_FS_ENCRYPTION
  • From: Niels de Vos
• [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
  • From: Niels de Vos
• [PATCH] fscrypt: pass super_block to fscrypt_put_master_key_activeref()
  • From: Eric Biggers
• Re: [PATCH v3] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• Re: [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
  • From: Christoph Hellwig
• [PATCH 6.0 125/197] fscrypt: fix keyring memory leak on mount failure
  • From: Greg Kroah-Hartman
• [PATCH 6.0 124/197] fscrypt: stop using keyrings subsystem for fscrypt_master_key
  • From: Greg Kroah-Hartman
• [PATCH 5.15 100/144] fscrypt: stop using keyrings subsystem for fscrypt_master_key
  • From: Greg Kroah-Hartman
• [PATCH 5.15 101/144] fscrypt: fix keyring memory leak on mount failure
  • From: Greg Kroah-Hartman
• [PATCH 5.10 080/118] fscrypt: simplify master key locking
  • From: Greg Kroah-Hartman
• [PATCH 5.10 082/118] fscrypt: fix keyring memory leak on mount failure
  • From: Greg Kroah-Hartman
• [PATCH 5.10 081/118] fscrypt: stop using keyrings subsystem for fscrypt_master_key
  • From: Greg Kroah-Hartman
• Re: Please apply "ext4,f2fs: fix readahead of verity data" to stable
  • From: Greg KH
• Re: [PATCH 3/3] blk-crypto: move __blk_crypto_cfg_supported to blk-crypto-internal.h
  • From: Eric Biggers
• Re: [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper
  • From: Eric Biggers
• Re: [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
  • From: Eric Biggers
• [PATCH 5.10] ext4,f2fs: fix readahead of verity data
  • From: Eric Biggers
• Please apply "ext4,f2fs: fix readahead of verity data" to stable
  • From: Eric Biggers
• [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper
  • From: Christoph Hellwig
• pass a struct block_device to the blk-crypto interfaces v2
  • From: Christoph Hellwig
• [PATCH 3/3] blk-crypto: move __blk_crypto_cfg_supported to blk-crypto-internal.h
  • From: Christoph Hellwig
• [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
  • From: Christoph Hellwig
• Re: [PATCH 5.10 0/3] fscrypt fixes for stable
  • From: Greg KH
• Re: [PATCH 5.15 0/2] fscrypt fixes for stable
  • From: Greg KH
• Re: [PATCH 6.0 0/2] fscrypt fixes for stable
  • From: Greg KH
• [PATCH 4/7] ext4: add missing validation of fast-commit record lengths
  • From: Eric Biggers
• [PATCH 5/7] ext4: fix unaligned memory access in ext4_fc_reserve_space()
  • From: Eric Biggers
• [PATCH 6/7] ext4: fix off-by-one errors in fast-commit block filling
  • From: Eric Biggers
• [PATCH 7/7] ext4: simplify fast-commit CRC calculation
  • From: Eric Biggers
• [PATCH 0/7] ext4 fast-commit fixes
  • From: Eric Biggers
• [PATCH 3/7] ext4: fix leaking uninitialized memory in fast-commit journal
  • From: Eric Biggers
• [PATCH 1/7] ext4: disable fast-commit of encrypted dir operations
  • From: Eric Biggers
• [PATCH 2/7] ext4: don't set up encryption key during jbd2 transaction
  • From: Eric Biggers
• [PATCH 5.10 3/3] fscrypt: fix keyring memory leak on mount failure
  • From: Eric Biggers
• [PATCH 5.10 1/3] fscrypt: simplify master key locking
  • From: Eric Biggers
• [PATCH 5.10 2/3] fscrypt: stop using keyrings subsystem for fscrypt_master_key
  • From: Eric Biggers
• [PATCH 5.10 0/3] fscrypt fixes for stable
  • From: Eric Biggers
• [PATCH 5.15 1/2] fscrypt: stop using keyrings subsystem for fscrypt_master_key
  • From: Eric Biggers
• [PATCH 5.15 2/2] fscrypt: fix keyring memory leak on mount failure
  • From: Eric Biggers
• [PATCH 5.15 0/2] fscrypt fixes for stable
  • From: Eric Biggers
• [PATCH 6.0 1/2] fscrypt: stop using keyrings subsystem for fscrypt_master_key
  • From: Eric Biggers
• [PATCH 6.0 2/2] fscrypt: fix keyring memory leak on mount failure
  • From: Eric Biggers
• [PATCH 6.0 0/2] fscrypt fixes for stable
  • From: Eric Biggers
• [xfstests PATCH v2 0/3] Fix test bugs related to fs.verity.require_signatures
  • From: Eric Biggers
• [xfstests PATCH v2 3/3] tests: fix some tests for systems with fs.verity.require_signatures=1
  • From: Eric Biggers
• [xfstests PATCH v2 2/3] generic/577: add missing file removal before empty file test
  • From: Eric Biggers
• [xfstests PATCH v2 1/3] common/verity: fix _fsv_have_hash_algorithm() with required signatures
  • From: Eric Biggers
• Re: [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
  • From: Christoph Hellwig
• Re: [PATCH 2/2] blk-crypto: add a blk_crypto_cfg_supported helper
  • From: Christoph Hellwig
• Re: [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
  • From: Eric Biggers
• Re: [PATCH 2/2] blk-crypto: add a blk_crypto_cfg_supported helper
  • From: Eric Biggers
• [xfstests PATCH 2/3] generic/577: add missing file removal before empty file test
  • From: Eric Biggers
• [xfstests PATCH 3/3] tests: fix some tests for systems with fs.verity.require_signatures=1
  • From: Eric Biggers
• [xfstests PATCH 0/3] Fix test bugs related to fs.verity.require_signatures
  • From: Eric Biggers
• [xfstests PATCH 1/3] common/verity: fix _fsv_have_hash_algorithm() with required signatures
  • From: Eric Biggers
• [PATCH 2/2] blk-crypto: add a blk_crypto_cfg_supported helper
  • From: Christoph Hellwig
• [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
  • From: Christoph Hellwig
• pass a struct block_device to the blk-crypto interfaces
  • From: Christoph Hellwig
• Re: [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Paul Crowley
• Re: [f2fs-dev] f2fs_empty_dir() can be extremely slow on malicious disk images
  • From: Chao Yu
• Re: [e2fsprogs PATCH v2] e2fsck: don't allow journal inode to have encrypt flag
  • From: Andreas Dilger
• Re: [e2fsprogs PATCH] e2fsck: don't allow journal inode to have encrypt flag
  • From: Eric Biggers
• [e2fsprogs PATCH v2] e2fsck: don't allow journal inode to have encrypt flag
  • From: Eric Biggers
• Re: [e2fsprogs PATCH] e2fsck: don't allow journal inode to have encrypt flag
  • From: Andreas Dilger
• Re: f2fs_empty_dir() can be extremely slow on malicious disk images
  • From: Chao Yu
• [PATCH v5 18/18] btrfs: allow encrypting compressed extents
  • From: Sweet Tea Dorminy
• [PATCH v5 16/18] btrfs: use correct name hash for nokey names
  • From: Sweet Tea Dorminy
• [PATCH v5 06/18] fscrypt: document btrfs' fscrypt quirks.
  • From: Sweet Tea Dorminy
• [PATCH v5 07/18] btrfs: disable various operations on encrypted inodes
  • From: Sweet Tea Dorminy
• [PATCH v5 13/18] btrfs: Add new FEATURE_INCOMPAT_ENCRYPT feature flag.
  • From: Sweet Tea Dorminy
• [PATCH v5 08/18] btrfs: start using fscrypt hooks
  • From: Sweet Tea Dorminy
• [PATCH v5 11/18] btrfs: store a fscrypt extent context per normal file extent
  • From: Sweet Tea Dorminy
• [PATCH v5 10/18] btrfs: translate btrfs encryption flags and encrypted inode flag
  • From: Sweet Tea Dorminy
• [PATCH v5 15/18] btrfs: permit searching for nokey names for removal
  • From: Sweet Tea Dorminy
• [PATCH v5 14/18] btrfs: implement fscrypt ioctls
  • From: Sweet Tea Dorminy
• [PATCH v5 12/18] btrfs: encrypt normal file extent data if appropriate
  • From: Sweet Tea Dorminy
• [PATCH v5 09/18] btrfs: add fscrypt_context items
  • From: Sweet Tea Dorminy
• [PATCH v5 17/18] btrfs: encrypt verity items
  • From: Sweet Tea Dorminy
• [PATCH v5 05/18] fscrypt: extent direct key policies for extent-based encryption
  • From: Sweet Tea Dorminy
• [PATCH v5 03/18] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
  • From: Sweet Tea Dorminy
• [PATCH v5 04/18] fscrypt: add extent-based encryption
  • From: Sweet Tea Dorminy
• [PATCH v5 02/18] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
  • From: Sweet Tea Dorminy
• [PATCH v5 01/18] fscrypt: expose fscrypt_nokey_name
  • From: Sweet Tea Dorminy
• [PATCH v5 00/18] btrfs: add fscrypt integration
  • From: Sweet Tea Dorminy
• Re: f2fs_empty_dir() can be extremely slow on malicious disk images
  • From: Wei Chen
• f2fs_empty_dir() can be extremely slow on malicious disk images
  • From: Eric Biggers
• [e2fsprogs PATCH] e2fsck: don't allow journal inode to have encrypt flag
  • From: Eric Biggers
• [PATCH] ext4: don't allow journal inode to have encrypt flag
  • From: Eric Biggers
• Re: [PATCH v4 08/21] btrfs: setup qstrings from dentrys using fscrypt helper
  • From: David Sterba
• Re: INFO: task hung in fscrypt_ioctl_set_policy
  • From: Wei Chen
• INFO: task hung in fscrypt_ioctl_set_policy
  • From: Wei Chen
• [PATCH 1/6] fsverity: support verification with tree block size < PAGE_SIZE
  • From: Eric Biggers
• [PATCH 6/6] ext4: allow verity with fs block size < PAGE_SIZE
  • From: Eric Biggers
• [PATCH 2/6] fsverity: support enabling with tree block size < PAGE_SIZE
  • From: Eric Biggers
• [PATCH 0/6] fsverity: support for non-4K pages
  • From: Eric Biggers
• [PATCH 5/6] fs/buffer.c: support fsverity in block_read_full_folio()
  • From: Eric Biggers
• [PATCH 4/6] f2fs: simplify f2fs_readpage_limit()
  • From: Eric Biggers
• [PATCH 3/6] ext4: simplify ext4_readpage_limit()
  • From: Eric Biggers
• [PATCH v3] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• Re: [PATCH v2 2/2] fsverity: stop using PG_error to track error status
  • From: Eric Biggers
• Re: [GIT PULL] fscrypt fix for 6.1-rc3
  • From: Linus Torvalds
• Re: [GIT PULL] fscrypt fix for 6.1-rc3
  • From: Eric Biggers
• Re: [GIT PULL] fscrypt fix for 6.1-rc3
  • From: pr-tracker-bot
• Re: [GIT PULL] fscrypt fix for 6.1-rc3
  • From: Linus Torvalds
• Re: [PATCH v4 02/21] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
  • From: Omar Sandoval
• [GIT PULL] fscrypt fix for 6.1-rc3
  • From: Eric Biggers
• Re: [PATCH v4 08/21] btrfs: setup qstrings from dentrys using fscrypt helper
  • From: Filipe Manana
• Re: [PATCH v4 00/21] btrfs: add fscrypt integration
  • From: David Sterba
• [PATCH v4 19/21] btrfs: permit searching for nokey names for removal
  • From: Sweet Tea Dorminy
• [PATCH v4 14/21] btrfs: translate btrfs encryption flags and encrypted inode flag
  • From: Sweet Tea Dorminy
• [PATCH v4 16/21] btrfs: encrypt normal file extent data if appropriate
  • From: Sweet Tea Dorminy
• [PATCH v4 15/21] btrfs: store a fscrypt extent context per normal file extent
  • From: Sweet Tea Dorminy
• [PATCH v4 21/21] btrfs: encrypt verity items
  • From: Sweet Tea Dorminy
• [PATCH v4 18/21] btrfs: implement fscrypt ioctls
  • From: Sweet Tea Dorminy
• [PATCH v4 09/21] btrfs: use struct fscrypt_str instead of struct qstr
  • From: Sweet Tea Dorminy
• [PATCH v4 11/21] btrfs: disable various operations on encrypted inodes
  • From: Sweet Tea Dorminy
• [PATCH v4 17/21] btrfs: Add new FEATURE_INCOMPAT_ENCRYPT feature flag.
  • From: Sweet Tea Dorminy
• [PATCH v4 20/21] btrfs: use correct name hash for nokey names
  • From: Sweet Tea Dorminy
• [PATCH v4 12/21] btrfs: start using fscrypt hooks
  • From: Sweet Tea Dorminy
• [PATCH v4 13/21] btrfs: add fscrypt_context items
  • From: Sweet Tea Dorminy
• [PATCH v4 10/21] btrfs: store directory encryption state
  • From: Sweet Tea Dorminy
• [PATCH v4 08/21] btrfs: setup qstrings from dentrys using fscrypt helper
  • From: Sweet Tea Dorminy
• [PATCH v4 07/21] btrfs: use struct qstr instead of name and namelen
  • From: Sweet Tea Dorminy
• [PATCH v4 06/21] fscrypt: document btrfs' fscrypt quirks.
  • From: Sweet Tea Dorminy
• [PATCH v4 05/21] fscrypt: direct key policies for extent-based encryption
  • From: Sweet Tea Dorminy
• [PATCH v4 03/21] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
  • From: Sweet Tea Dorminy
• [PATCH v4 02/21] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
  • From: Sweet Tea Dorminy
• [PATCH v4 04/21] fscrypt: add extent-based encryption
  • From: Sweet Tea Dorminy
• [PATCH v4 00/21] btrfs: add fscrypt integration
  • From: Sweet Tea Dorminy
• [PATCH v4 01/21] fscrypt: expose fscrypt_nokey_name
  • From: Sweet Tea Dorminy
• Re: [PATCH v3 15/22] btrfs: encrypt normal file extent data if appropriate
  • From: Josef Bacik
• Re: [PATCH v3 12/22] btrfs: add fscrypt_context items
  • From: Josef Bacik
• Re: [PATCH v3 08/22] btrfs: use struct fscrypt_str instead of struct qstr
  • From: Josef Bacik
• Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
  • From: Sweet Tea Dorminy
• Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
  • From: Eric Biggers
• Re: [PATCH v3 00/22] btrfs: add fscrypt integration
  • From: David Sterba
• Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
  • From: Sweet Tea Dorminy
• Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
  • From: Sweet Tea Dorminy
• Re: [PATCH v3 05/22] fscrypt: document btrfs' fscrypt quirks.
  • From: Sweet Tea Dorminy
• Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
  • From: Eric Biggers
• Re: [PATCH v3 05/22] fscrypt: document btrfs' fscrypt quirks.
  • From: Eric Biggers
• Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
  • From: Eric Biggers
• Re: [PATCH v3 00/22] btrfs: add fscrypt integration
  • From: Eric Biggers
• Re: [PATCH v3 02/22] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
  • From: Josef Bacik
• [PATCH v3 21/22] fscrypt: add flag allowing partially-encrypted directories
  • From: Sweet Tea Dorminy
• [PATCH v3 16/22] btrfs: Add new FEATURE_INCOMPAT_ENCRYPT feature flag.
  • From: Sweet Tea Dorminy
• [PATCH v3 17/22] btrfs: implement fscrypt ioctls
  • From: Sweet Tea Dorminy
• [PATCH v3 13/22] btrfs: translate btrfs encryption flags and encrypted inode flag
  • From: Sweet Tea Dorminy
• [PATCH v3 08/22] btrfs: use struct fscrypt_str instead of struct qstr
  • From: Sweet Tea Dorminy
• [PATCH v3 09/22] btrfs: store directory encryption state
  • From: Sweet Tea Dorminy
• [PATCH v3 10/22] btrfs: disable various operations on encrypted inodes
  • From: Sweet Tea Dorminy
• [PATCH v3 22/22] btrfs: encrypt verity items
  • From: Sweet Tea Dorminy
• [PATCH v3 20/22] btrfs: adapt lookup for partially encrypted directories
  • From: Sweet Tea Dorminy
• [PATCH v3 19/22] btrfs: use correct name hash for nokey names
  • From: Sweet Tea Dorminy
• [PATCH v3 18/22] btrfs: permit searching for nokey names for removal
  • From: Sweet Tea Dorminy
• [PATCH v3 15/22] btrfs: encrypt normal file extent data if appropriate
  • From: Sweet Tea Dorminy
• [PATCH v3 14/22] btrfs: store a fscrypt extent context per normal file extent
  • From: Sweet Tea Dorminy
• [PATCH v3 11/22] btrfs: start using fscrypt hooks
  • From: Sweet Tea Dorminy
• [PATCH v3 12/22] btrfs: add fscrypt_context items
  • From: Sweet Tea Dorminy
• [PATCH v3 04/22] fscrypt: add extent-based encryption
  • From: Sweet Tea Dorminy
• [PATCH v3 07/22] btrfs: setup qstrings from dentrys using fscrypt helper
  • From: Sweet Tea Dorminy
• [PATCH v3 05/22] fscrypt: document btrfs' fscrypt quirks.
  • From: Sweet Tea Dorminy
• [PATCH v3 03/22] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
  • From: Sweet Tea Dorminy
• [PATCH v3 06/22] btrfs: use struct qstr instead of name and namelen
  • From: Sweet Tea Dorminy
• [PATCH v3 02/22] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
  • From: Sweet Tea Dorminy
• [PATCH v3 01/22] fscrypt: expose fscrypt_nokey_name
  • From: Sweet Tea Dorminy
• [PATCH v3 00/22] btrfs: add fscrypt integration
  • From: Sweet Tea Dorminy
• Re: [PATCH] fscrypt: fix keyring memory leak on mount failure
  • From: Christian Brauner
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Stephen Rothwell
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Eric Biggers
• Re: Please don't backport "fscrypt: stop using keyrings subsystem for fscrypt_master_key" to stable until it's ready
  • From: Greg Kroah-Hartman
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Stephen Rothwell
• Re: [PATCH] fscrypt: fix keyring memory leak on mount failure
  • From: Eric Biggers
• Please don't backport "fscrypt: stop using keyrings subsystem for fscrypt_master_key" to stable until it's ready
  • From: Eric Biggers
• Re: [syzbot] memory leak in crypto_create_tfm_node
  • From: Eric Biggers
• Re: [syzbot] memory leak in crypto_create_tfm_node
  • From: Herbert Xu
• Re: [man-pages PATCH v4] statx.2, open.2: document STATX_DIOALIGN
  • From: Alejandro Colomar
• Re: [syzbot] memory leak in crypto_create_tfm_node
  • From: Dmitry Vyukov
• Re: [syzbot] memory leak in crypto_create_tfm_node
  • From: Herbert Xu
• Re: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
  • From: Eric Biggers
• [man-pages PATCH v4] statx.2, open.2: document STATX_DIOALIGN
  • From: Eric Biggers
• [PATCH] fscrypt: fix keyring memory leak on mount failure
  • From: Eric Biggers
• Semantic newlines (was: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN)
  • From: Alejandro Colomar
• Re: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
  • From: Darrick J. Wong
• Re: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
  • From: Alejandro Colomar
• Re: [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
  • From: Darrick J. Wong
• Re: [PATCH] fscrypt: fix lockdep warning
  • From: Yu Zhao
• Re: [PATCH] fscrypt: fix lockdep warning
  • From: Eric Biggers
• [PATCH] fscrypt: fix lockdep warning
  • From: Yu Zhao
• [man-pages PATCH v3] statx.2, open.2: document STATX_DIOALIGN
  • From: Eric Biggers
• Re: [GIT PULL] fsverity updates for 6.1
  • From: pr-tracker-bot
• Re: [GIT PULL] fscrypt updates for 6.1
  • From: pr-tracker-bot
• Re: [GIT PULL] STATX_DIOALIGN for 6.1
  • From: pr-tracker-bot
• [GIT PULL] STATX_DIOALIGN for 6.1
  • From: Eric Biggers
• [GIT PULL] fsverity updates for 6.1
  • From: Eric Biggers
• [GIT PULL] fscrypt updates for 6.1
  • From: Eric Biggers
• [RFC PATCH v6 3/4] blk-crypto: add ioctls to create and prepare hardware-wrapped keys
  • From: Eric Biggers
• [RFC PATCH v6 2/4] blk-crypto: show supported key types in sysfs
  • From: Eric Biggers
• [RFC PATCH v6 1/4] blk-crypto: add basic hardware-wrapped key support
  • From: Eric Biggers
• [RFC PATCH v6 0/4] Support for hardware-wrapped inline encryption keys
  • From: Eric Biggers
• [RFC PATCH v6 4/4] fscrypt: add support for hardware-wrapped keys
  • From: Eric Biggers
• Re: [PATCH v3] btrfs-progs: receive: add support for fs-verity
  • From: David Sterba
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: David Sterba
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: David Sterba
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: Bradley M. Kuhn
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: J Lovejoy
• Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
  • From: Sweet Tea Dorminy
• Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
  • From: Neal Gompa
• Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
  • From: Anand Jain
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Stephen Rothwell
• Re: [PATCH v2 12/20] btrfs: start using fscrypt hooks.
  • From: Eric Biggers
• Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
  • From: Eric Biggers
• Re: [PATCH v2 16/20] btrfs: Add new FEATURE_INCOMPAT_FSCRYPT feature flag.
  • From: Eric Biggers
• Re: [PATCH v2 05/20] fscrypt: add extent-based encryption
  • From: Eric Biggers
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Eric Biggers
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: Chris Mason
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: David Sterba
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: Christoph Hellwig
• Re: [PATCH v2 16/20] btrfs: Add new FEATURE_INCOMPAT_FSCRYPT feature flag.
  • From: David Sterba
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: David Sterba
• Re: [PATCH v2 15/20] btrfs: store a fscrypt extent context per normal file extent
  • From: David Sterba
• Re: [PATCH v2 19/20] btrfs: encrypt normal file extent data if appropriate
  • From: Josef Bacik
• Re: [PATCH v2 18/20] btrfs: adapt directory read and lookup to potentially encrypted filenames
  • From: Josef Bacik
• Re: [PATCH v2 14/20] btrfs: translate btrfs encryption flags and encrypted inode flag.
  • From: Josef Bacik
• Re: [PATCH v2 13/20] btrfs: add fscrypt_context items.
  • From: Josef Bacik
• Re: [PATCH v2 12/20] btrfs: start using fscrypt hooks.
  • From: Josef Bacik
• Re: [PATCH v2 10/20] btrfs: factor a fscrypt_name matching method
  • From: Josef Bacik
• Re: [PATCH v2 09/20] btrfs: setup fscrypt_names from dentrys using helper
  • From: Josef Bacik
• Re: [PATCH v2 07/20] btrfs: store directory's encryption state
  • From: Josef Bacik
• Re: [PATCH v2 06/20] fscrypt: document btrfs' fscrypt quirks.
  • From: Josef Bacik
• Re: [PATCH v2 05/20] fscrypt: add extent-based encryption
  • From: Josef Bacik
• Re: [PATCH v2 04/20] fscrypt: allow fscrypt_generate_iv() to distinguish filenames
  • From: Josef Bacik
• Re: [PATCH v2 03/20] fscrypt: add fscrypt_have_same_policy() to check inode compatibility
  • From: Josef Bacik
• Re: [PATCH v2 02/20] fscrypt: add flag allowing partially-encrypted directories
  • From: Josef Bacik
• Re: [PATCH v2 01/20] fscrypt: expose fscrypt_nokey_name
  • From: Josef Bacik
• Re: [PATCH v2 15/20] btrfs: store a fscrypt extent context per normal file extent
  • From: Sweet Tea Dorminy
• Re: [PATCH v2 20/20] btrfs: implement fscrypt ioctls
  • From: David Sterba
• Re: [PATCH v2 17/20] btrfs: reuse encrypted filename hash when possible.
  • From: David Sterba
• Re: [PATCH v2 15/20] btrfs: store a fscrypt extent context per normal file extent
  • From: David Sterba
• Re: [PATCH v2 13/20] btrfs: add fscrypt_context items.
  • From: David Sterba
• Re: [PATCH v2 12/20] btrfs: start using fscrypt hooks.
  • From: Sweet Tea Dorminy
• Re: [PATCH v2 12/20] btrfs: start using fscrypt hooks.
  • From: David Sterba
• Re: [PATCH v2 11/20] btrfs: disable various operations on encrypted inodes
  • From: David Sterba
• Re: [PATCH v2 08/20] btrfs: use fscrypt_names instead of name/len everywhere.
  • From: David Sterba
• Re: [PATCH v2 05/20] fscrypt: add extent-based encryption
  • From: Omar Sandoval
• Re: [PATCH v2 00/20] btrfs: add fscrypt integration
  • From: David Sterba
• Re: [PATCH v5 1/8] statx: add direct I/O alignment information
  • From: Christian Brauner
• Re: [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices
  • From: Christian Brauner
• Re: [PATCH 1/2] fstests: fscrypt: enable btrfs testing.
  • From: Zorro Lang
• Re: [PATCH v2 00/20] btrfs: add fscrypt integration
  • From: Sweet Tea Dorminy
• Re: [PATCH v2 00/20] btrfs: add fscrypt integration
  • From: Eric Biggers
• Re: [PATCH v2 00/20] btrfs: add fscrypt integration
  • From: Sweet Tea Dorminy
• Re: [PATCH v2 00/20] btrfs: add fscrypt integration
  • From: Eric Biggers
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Eric Biggers
• Re: [f2fs-dev] [PATCH v2 2/2] fsverity: stop using PG_error to track error status
  • From: Chao Yu
• Re: [f2fs-dev] [PATCH v2 1/2] fscrypt: stop using PG_error to track error status
  • From: Chao Yu
• Re: [PATCH v5 8/8] xfs: support STATX_DIOALIGN
  • From: Christoph Hellwig
• Re: [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices
  • From: Christoph Hellwig
• [PATCH v2 16/20] btrfs: Add new FEATURE_INCOMPAT_FSCRYPT feature flag.
  • From: Sweet Tea Dorminy
• [PATCH v2 11/20] btrfs: disable various operations on encrypted inodes
  • From: Sweet Tea Dorminy
• [PATCH v2 14/20] btrfs: translate btrfs encryption flags and encrypted inode flag.
  • From: Sweet Tea Dorminy
• [PATCH v2 17/20] btrfs: reuse encrypted filename hash when possible.
  • From: Sweet Tea Dorminy
• [PATCH v2 20/20] btrfs: implement fscrypt ioctls
  • From: Sweet Tea Dorminy
• [PATCH v2 18/20] btrfs: adapt directory read and lookup to potentially encrypted filenames
  • From: Sweet Tea Dorminy
• [PATCH v2 19/20] btrfs: encrypt normal file extent data if appropriate
  • From: Sweet Tea Dorminy
• [PATCH v2 12/20] btrfs: start using fscrypt hooks.
  • From: Sweet Tea Dorminy