block: show crypto capabilities in sysfs
Subsystems (4)
v4 cover block: show crypto capabilities in sysfs
This series adds sysfs files that expose the inline encryption capabilities of request queues.
Patches 1 and 2 are some related cleanups for existing blk-sysfs code. Patch 3 is the real change; see there for more details.
This series applies to v5.17-rc1.
Changed v3 => v4:
- Reworded a comment in patch 2.
- Updated dates in sysfs documentation.
- Added more Reviewed-by tags.
Changed v2 => v3:
- Moved the documentation into Documentation/ABI/stable/sysfs-block, and improved it a bit.
- Write "/sys/block/" instead of "/sys/class/block/".
- Added Reviewed-by tags.
Changed v1 => v2:
- Use sysfs_emit() instead of sprintf().
- Use __ATTR_RO().
Eric Biggers (3):
block: simplify calling convention of elv_unregister_queue()
block: don't delete queue kobject before its children
blk-crypto: show crypto capabilities in sysfs
Documentation/ABI/stable/sysfs-block | 49 ++++++++ block/Makefile | 3 +- block/blk-crypto-internal.h | 12 ++ block/blk-crypto-sysfs.c | 172 +++++++++++++++++++++++++++ block/blk-crypto.c | 3 + block/blk-sysfs.c | 17 ++- block/elevator.c | 8 +- include/linux/blkdev.h | 1 + 8 files changed, 255 insertions(+), 10 deletions(-) create mode 100644 block/blk-crypto-sysfs.c
base-commit: e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
Signature · 1 line
2.34.1
PATCH v4 1/3 block: simplify calling convention of elv_unregister_queue()
From: Eric Biggers <[email protected]>
Make elv_unregister_queue() a no-op if q->elevator is NULL or is not registered.
This simplifies the existing callers, as well as the future caller in the error path of blk_register_queue().
Also don't bother checking whether q is NULL, since it never is.
--- block/blk-sysfs.c | 3 +-- block/elevator.c | 8 ++++---- 2 files changed, 5 insertions(+), 6 deletions(-)
block/blk-sysfs.c +1 -2
@@ -960,8 +960,7 @@ void blk_unregister_queue(struct gendisk *disk)blk_trace_remove_sysfs (disk_to_dev (disk));mutex_lock (&q->sysfs_lock); -if (q->elevator) -elv_unregister_queue (q); +elv_unregister_queue (q);disk_unregister_independent_access_ranges (disk);mutex_unlock (&q->sysfs_lock);mutex_unlock (&q->sysfs_dir_lock);
block/elevator.c +4 -4
@@ -516,9 +516,11 @@ int elv_register_queue(struct request_queue *q, bool uevent)void elv_unregister_queue (struct request_queue *q) { +struct elevator_queue *e = q->elevator; +lockdep_assert_held (&q->sysfs_lock); -if (q) { +if (e && e->registered) {struct elevator_queue *e = q->elevator;kobject_uevent (&e->kobj,KOBJ_REMOVE );
@@ -593,9 +595,7 @@ int elevator_switch_mq(struct request_queue *q,lockdep_assert_held (&q->sysfs_lock);if (q->elevator) { -if (q->elevator->registered) -elv_unregister_queue (q); - +elv_unregister_queue (q);ioc_clear_queue (q);blk_mq_sched_free_rqs (q);elevator_exit (q);
Signature · 1 line
2.34.1
Re: [PATCH v4 1/3] block: simplify calling convention of elv_unregister_queue()
Quoted 5 lines · Eric Biggers
From: Eric Biggers <[email protected]>
Make
elv_unregister_queue()a no-op ifq->elevatoris NULL or is not registered.
Quoted 8 lines
This simplifies the existing callers, as well as the future caller in the error path of
blk_register_queue().Also don't bother checking whether q is NULL, since it never is.
Reviewed-by Hannes Reinecke <[email protected]>Reviewed-by Bart Van Assche <[email protected]>Signed-off-by Eric Biggers <[email protected]>
Looks good,
PATCH v4 2/3 block: don't delete queue kobject before its children
In reply to Eric BiggersFrom: Eric Biggers <[email protected]>
kobjects aren't supposed to be deleted before their child kobjects are deleted. Apparently this is usually benign; however, a WARN will be triggered if one of the child kobjects has a named attribute group:
sysfs group 'modes' not found for kobject 'crypto'
WARNING: CPU: 0 PID: 1 at fs/sysfs/group.c:278 sysfs_remove_group+0x72/0x80
...
Call Trace:
sysfs_remove_groups+0x29/0x40 fs/sysfs/group.c:312
__kobject_del+0x20/0x80 lib/kobject.c:611
kobject_cleanup+0xa4/0x140 lib/kobject.c:696
kobject_release lib/kobject.c:736 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x53/0x70 lib/kobject.c:753
blk_crypto_sysfs_unregister+0x10/0x20 block/blk-crypto-sysfs.c:159
blk_unregister_queue+0xb0/0x110 block/blk-sysfs.c:962
del_gendisk+0x117/0x250 block/genhd.c:610Fix this by moving the kobject_del() and the corresponding kobject_uevent() to the correct place.
--- block/blk-sysfs.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
block/blk-sysfs.c +5 -3
@@ -954,15 +954,17 @@ void blk_unregister_queue(struct gendisk *disk)*/ if (queue_is_mq (q))blk_mq_unregister_dev (disk_to_dev (disk), q); - -kobject_uevent (&q->kobj,KOBJ_REMOVE ); -kobject_del (&q->kobj);blk_trace_remove_sysfs (disk_to_dev (disk));mutex_lock (&q->sysfs_lock);elv_unregister_queue (q);disk_unregister_independent_access_ranges (disk);mutex_unlock (&q->sysfs_lock); + +/* Now that we've deleted all child objects, we can delete the queue. */ +kobject_uevent (&q->kobj,KOBJ_REMOVE ); +kobject_del (&q->kobj); +mutex_unlock (&q->sysfs_dir_lock);kobject_put (&disk_to_dev (disk)->kobj);
Signature · 1 line
2.34.1
Re: [PATCH v4 2/3] block: don't delete queue kobject before its children
Looks good,
PATCH v4 3/3 blk-crypto: show crypto capabilities in sysfs
In reply to Eric BiggersFrom: Eric Biggers <[email protected]>
Add sysfs files that expose the inline encryption capabilities of request queues:
/sys/block/$disk/queue/crypto/max_dun_bits /sys/block/$disk/queue/crypto/modes/$mode /sys/block/$disk/queue/crypto/num_keyslots
Userspace can use these new files to decide what encryption settings to use, or whether to use inline encryption at all. This also brings the crypto capabilities in line with the other queue properties, which are already discoverable via the queue directory in sysfs.
Design notes:
- Place the new files in a new subdirectory "crypto" to group them together and to avoid complicating the main "queue" directory. This also makes it possible to replace "crypto" with a symlink later if we ever make the blk_crypto_profiles into real kobjects (see below).
- It was necessary to define a new kobject that corresponds to the crypto subdirectory. For now, this kobject just contains a pointer to the blk_crypto_profile. Note that multiple queues (and hence multiple such kobjects) may refer to the same blk_crypto_profile.
An alternative design would more closely match the current kernel data structures: the blk_crypto_profile could be a kobject itself, located directly under the host controller device's kobject, while /sys/block/$disk/queue/crypto would be a symlink to it.
I decided not to do that for now because it would require a lot more changes, such as no longer embedding blk_crypto_profile in other structures, and also because I'm not sure we can rule out moving the crypto capabilities into 'struct queue_limits' in the future. (Even if multiple queues share the same crypto engine, maybe the supported data unit sizes could differ due to other queue properties.) It would also still be possible to switch to that design later without breaking userspace, by replacing the directory with a symlink.
- Use "max_dun_bits" instead of "max_dun_bytes". Currently, the kernel internally stores this value in bytes, but that's an implementation detail. It probably makes more sense to talk about this value in bits, and choosing bits is more future-proof.
- "modes" is a sub-subdirectory, since there may be multiple supported crypto modes, sysfs is supposed to have one value per file, and it makes sense to group all the mode files together.
- Each mode had to be named. The crypto API names like "xts(aes)" are not appropriate because they don't specify the key size. Therefore, I assigned new names. The exact names chosen are arbitrary, but they happen to match the names used in log messages in fs/crypto/.
- The "num_keyslots" file is a bit different from the others in that it is only useful to know for performance reasons. However, it's included as it can still be useful. For example, a user might not want to use inline encryption if there aren't very many keyslots.
--- Documentation/ABI/stable/sysfs-block | 49 ++++++++ block/Makefile | 3 +- block/blk-crypto-internal.h | 12 ++ block/blk-crypto-sysfs.c | 172 +++++++++++++++++++++++++++ block/blk-crypto.c | 3 + block/blk-sysfs.c | 6 + include/linux/blkdev.h | 1 + 7 files changed, 245 insertions(+), 1 deletion(-) create mode 100644 block/blk-crypto-sysfs.c
Documentation/ABI/stable/sysfs-block +49 -0
@@ -155,6 +155,55 @@ Description: last zone of the device which may be smaller. +What: /sys/block/<disk>/queue/crypto/ +Date: February 2022 +Contact: [email protected] +Description: + The presence of this subdirectory of /sys/block/<disk>/queue/ + indicates that the device supports inline encryption. This + subdirectory contains files which describe the inline encryption + capabilities of the device. For more information about inline + encryption, refer to Documentation/block/inline-encryption.rst. + + +What: /sys/block/<disk>/queue/crypto/max_dun_bits +Date: February 2022 +Contact: [email protected] +Description: + [RO] This file shows the maximum length, in bits, of data unit + numbers accepted by the device in inline encryption requests. + + +What: /sys/block/<disk>/queue/crypto/modes/<mode> +Date: February 2022 +Contact: [email protected] +Description: + [RO] For each crypto mode (i.e., encryption/decryption + algorithm) the device supports with inline encryption, a file + will exist at this location. It will contain a hexadecimal + number that is a bitmask of the supported data unit sizes, in + bytes, for that crypto mode. + + Currently, the crypto modes that may be supported are: + + * AES-256-XTS + * AES-128-CBC-ESSIV + * Adiantum + + For example, if a device supports AES-256-XTS inline encryption + with data unit sizes of 512 and 4096 bytes, the file + /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and + will contain "0x1200". + + +What: /sys/block/<disk>/queue/crypto/num_keyslots +Date: February 2022 +Contact: [email protected] +Description: + [RO] This file shows the number of keyslots the device has for + use with inline encryption. + + What: /sys/block/<disk>/queue/dax Date: June 2016 Contact: [email protected]
block/Makefile +2 -1
@@ -36,6 +36,7 @@ obj-$(CONFIG_BLK_DEBUG_FS) += blk-mq-debugfs.o obj-$(CONFIG_BLK_DEBUG_FS_ZONED)+= blk-mq-debugfs-zoned.o obj-$(CONFIG_BLK_SED_OPAL) += sed-opal.o obj-$(CONFIG_BLK_PM) += blk-pm.o -obj-$(CONFIG_BLK_INLINE_ENCRYPTION) += blk-crypto.o blk-crypto-profile.o +obj-$(CONFIG_BLK_INLINE_ENCRYPTION) += blk-crypto.o blk-crypto-profile.o \ + blk-crypto-sysfs.o obj-$(CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK) += blk-crypto-fallback.o obj-$(CONFIG_BLOCK_HOLDER_DEPRECATED) += holder.o
block/blk-crypto-internal.h +12 -0
@@ -11,6 +11,7 @@/* Represents a crypto mode supported by blk-crypto */ struct blk_crypto_mode { +const char *name;/* name of this mode, shown in sysfs */ const char *cipher_str;/* crypto API name (for fallback case) */ unsigned int keysize;/* key size in bytes */ unsigned int ivsize;/* iv size in bytes */
@@ -20,6 +21,10 @@ extern const struct blk_crypto_mode blk_crypto_modes[];#ifdef CONFIG_BLK_INLINE_ENCRYPTION +int blk_crypto_sysfs_register (struct request_queue *q); + +void blk_crypto_sysfs_unregister (struct request_queue *q); +void bio_crypt_dun_increment (u64 dun[BLK_CRYPTO_DUN_ARRAY_SIZE ],unsigned int inc);
@@ -62,6 +67,13 @@ static inline bool blk_crypto_rq_is_encrypted(struct request *rq)#else /* CONFIG_BLK_INLINE_ENCRYPTION */ +static inline int blk_crypto_sysfs_register (struct request_queue *q) +{ +return 0 ; +} + +static inline void blk_crypto_sysfs_unregister (struct request_queue *q) { } +static inline bool bio_crypt_rq_ctx_compatible (struct request *rq,struct bio *bio) {
block/blk-crypto-sysfs.c new file +172 -0
172 lines not on this page · raw message
block/blk-crypto.c +3 -0
@@ -19,16 +19,19 @@const struct blk_crypto_mode blk_crypto_modes[] = { [BLK_ENCRYPTION_MODE_AES_256_XTS ] = { + .name ="AES-256-XTS" , .cipher_str ="xts(aes)" , .keysize =64 , .ivsize =16 , }, [BLK_ENCRYPTION_MODE_AES_128_CBC_ESSIV ] = { + .name ="AES-128-CBC-ESSIV" , .cipher_str ="essiv(cbc(aes),sha256)" , .keysize =16 , .ivsize =16 , }, [BLK_ENCRYPTION_MODE_ADIANTUM ] = { + .name ="Adiantum" , .cipher_str ="adiantum(xchacha12,aes)" , .keysize =32 , .ivsize =32 ,
block/blk-sysfs.c +6 -0
@@ -880,6 +880,10 @@ int blk_register_queue(struct gendisk *disk) goto put_dev; } + ret =blk_crypto_sysfs_register (q); +if (ret) + goto put_dev; +blk_queue_flag_set (QUEUE_FLAG_REGISTERED , q);wbt_enable_default (q);blk_throtl_register_queue (q);
@@ -910,6 +914,7 @@ int blk_register_queue(struct gendisk *disk)return ret; put_dev: +elv_unregister_queue (q);disk_unregister_independent_access_ranges (disk);mutex_unlock (&q->sysfs_lock);mutex_unlock (&q->sysfs_dir_lock);
@@ -954,6 +959,7 @@ void blk_unregister_queue(struct gendisk *disk)*/ if (queue_is_mq (q))blk_mq_unregister_dev (disk_to_dev (disk), q); +blk_crypto_sysfs_unregister (q);blk_trace_remove_sysfs (disk_to_dev (disk));mutex_lock (&q->sysfs_lock);
include/linux/blkdev.h +1 -0
@@ -262,6 +262,7 @@ struct request_queue {#ifdef CONFIG_BLK_INLINE_ENCRYPTION struct blk_crypto_profile *crypto_profile; +struct kobject *crypto_kobject;#endif unsigned int rq_timeout;
Signature · 1 line
2.34.1
Quoted 19 lines · Eric Biggers
This series adds sysfs files that expose the inline encryption capabilities of request queues.
Patches 1 and 2 are some related cleanups for existing blk-sysfs code. Patch 3 is the real change; see there for more details.
This series applies to v5.17-rc1.
Changed v3 => v4:
- Reworded a comment in patch 2.
- Updated dates in sysfs documentation.
- Added more Reviewed-by tags.Changed v2 => v3:
- Moved the documentation intoDocumentation/ABI/stable/sysfs-block, and improved it a bit.
- Write "/sys/block/" instead of "/sys/class/block/".
- Added Reviewed-by tags.
Quoted 9 lines
Changed v1 => v2:
- Usesysfs_emit()instead ofsprintf().
- Use__ATTR_RO().Eric Biggers (3):
block: simplify calling convention ofelv_unregister_queue()
block: don't delete queue kobject before its children
blk-crypto: show crypto capabilities in sysfs
Any more feedback on this?
- Eric
Quoted 24 lines · Eric Biggers
Quoted 23 lines · Eric Biggers
This series adds sysfs files that expose the inline encryption capabilities of request queues.
Patches 1 and 2 are some related cleanups for existing blk-sysfs code. Patch 3 is the real change; see there for more details.
This series applies to v5.17-rc1.
Changed v3 => v4:
- Reworded a comment in patch 2.
- Updated dates in sysfs documentation.
- Added more Reviewed-by tags.Changed v2 => v3:
- Moved the documentation intoDocumentation/ABI/stable/sysfs-block, and improved it a bit.
- Write "/sys/block/" instead of "/sys/class/block/".
- Added Reviewed-by tags.Changed v1 => v2:
- Usesysfs_emit()instead ofsprintf().
- Use__ATTR_RO().
Quoted 8 lines
Quoted 5 lines
Eric Biggers (3):
block: simplify calling convention ofelv_unregister_queue()
block: don't delete queue kobject before its children
blk-crypto: show crypto capabilities in sysfsAny more feedback on this?
Jens, can you apply this for 5.18? Is there anything else you're waiting for?
- Eric
Quoted 9 lines · Eric Biggers
This series adds sysfs files that expose the inline encryption capabilities of request queues.
Patches 1 and 2 are some related cleanups for existing blk-sysfs code. Patch 3 is the real change; see there for more details.
This series applies to v5.17-rc1.
[...]
Applied, thanks!
[1/3] block: simplify calling convention of elv_unregister_queue()
commit: f5ec592dd3bcf7c91f7c262a7f5011e001d269cd
[2/3] block: don't delete queue kobject before its children
commit: 0f69288253e9fc7c495047720e523b9f1aba5712
[3/3] blk-crypto: show crypto capabilities in sysfs
commit: 20f01f163203666010ee1560852590a0c0572726Best regards,
Signature · 1 line
Jens Axboe