Re: [dm-devel] [BUG] multipath-tools: missing internal values (multipath -t)

On 04/27/2017 09:10 AM, Christophe Varoqui wrote: > The config outputed should be usable, so a comment could be printed for the > keywords you suggest printing as the default for. > > Example: > > # no_path_retry > > or simply > > # no_path_retry Undefined

Re: [dm-devel] [PATCH 1/2] multipath: Merge the DELL MD3xxx device configs

On 04/13/2017 12:15 AM, Benjamin Marzinski wrote: > All of the Dell MD3xxx configs are identical, so we can't just use > one config for them. If you do that to simplify the config file or minimize the number of RDAC entries. More of them, from (NETAPP|LSI|ENGENIO) IBM SGI STK SUN, can be

Re: [dm-devel] [mdadm PATCH] Create: tell udev md device is not ready when first created.

On 03/05/17 15:13, Peter Rajnoha wrote: > There's a difference though - when you're *creating* a completely new > device that is an abstraction over existing devices, you (most of the > time) expect that new device to be initialized. For those corner cases > where people do need to keep the old

[dm-devel] [RFC 09/10] ima: move to generic async completion

ima starts several async. crypto ops and waits for their completions. Move it over to generic code doing the same. Signed-off-by: Gilad Ben-Yossef --- security/integrity/ima/ima_crypto.c | 56 +++-- 1 file changed, 17 insertions(+), 39

[dm-devel] [RFC 01/10] crypto: factor async completion for general use

Invoking a possibly async. crypto op and waiting for completion while correctly handling backlog processing is a common task in the crypto API implementation and outside users of it. This patch re-factors one of the in crypto API implementation in preparation for using it across the board instead

[dm-devel] [RFC 03/10] crypto: move drbg to generic async completion

DRBG is starting an async. crypto op and waiting for it complete. Move it over to generic code doing the same. As part of the move the wait for op completion lost its _interruptible property. However, since each invocation is supposed to be short and since no other user in the kernel does the

[dm-devel] [RFC 06/10] dm: move dm-verity to generic async completion

dm-verity is starting async. crypto ops and waiting for them to complete. Move it over to generic code doing the same. Signed-off-by: Gilad Ben-Yossef --- drivers/md/dm-verity-target.c | 81 +++ drivers/md/dm-verity.h| 5 ---

[dm-devel] [RFC 04/10] crypto: move gcm to generic async completion

gcm is starting an async. crypto op and waiting for it complete. Move it over to generic code doing the same. Signed-off-by: Gilad Ben-Yossef --- crypto/gcm.c | 34 ++ 1 file changed, 6 insertions(+), 28 deletions(-) diff --git

[dm-devel] [RFC 02/10] crypto: move pub key to generic async completion

public_key_verify_signature() is starting an async crypto op and waiting for it to complete. Move it over to generic code doing the same. This also fixes a bug in which the code was passing the CRYPTO_TFM_REQ_MAY_BACKLOG flag to akcipher_request_set_callback() but was not correctly testing for

[dm-devel] [RFC 00/10] introduce crypto wait for async op function

Many users of kernel async. crypto services have a pattern of starting an async. crypto op and than using a completion to wait for it to end, resulting of the same code repeating itself in multiple places, sometime with errors. This patch aims to introduce a generic "wait for async. crypto op to