From: Farhan Ali <alifm@linux.ibm.com> To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: mst@redhat.com, qemu-devel@nongnu.org, arei.gonglei@huawei.com, longpeng2@huawei.com, pasic@linux.ibm.com, frankja@linux.ibm.com, borntraeger@de.ibm.com, alifm@linux.ibm.com Subject: [RFC v1 0/2] Detect & register virtio-crypto algos only if it can be supported by backend Date: Fri, 8 Jun 2018 15:08:45 -0400 [thread overview] Message-ID: <cover.1528462918.git.alifm@linux.ibm.com> (raw) Hi, Currently the Linux virtio-crypto driver registers the crypto algorithm without verifying if the backend actually supports the algorithm. This kernel patch series adds support for registering algorithm with Linux crypto layer, only if the algorithm is supported by the backend device. This also makes the driver more compliant with the virtio-crypto spec [1]. I would appreciate any feedback or comments on this. Thank you Farhan Reference --------- [1] Virtio crypto spec proposal https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg00816.html Farhan Ali (2): crypto/virtio-crypto: Read crypto services and algorithm masks crypto/virtio-crypto: Register an algo only if it's supported drivers/crypto/virtio/virtio_crypto_algs.c | 110 ++++++++++++++++++--------- drivers/crypto/virtio/virtio_crypto_common.h | 25 +++++- drivers/crypto/virtio/virtio_crypto_core.c | 29 +++++++ drivers/crypto/virtio/virtio_crypto_mgr.c | 81 ++++++++++++++++++-- 4 files changed, 201 insertions(+), 44 deletions(-) -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Farhan Ali <alifm@linux.ibm.com> To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: mst@redhat.com, qemu-devel@nongnu.org, arei.gonglei@huawei.com, longpeng2@huawei.com, pasic@linux.ibm.com, frankja@linux.ibm.com, borntraeger@de.ibm.com, alifm@linux.ibm.com Subject: [Qemu-devel] [RFC v1 0/2] Detect & register virtio-crypto algos only if it can be supported by backend Date: Fri, 8 Jun 2018 15:08:45 -0400 [thread overview] Message-ID: <cover.1528462918.git.alifm@linux.ibm.com> (raw) Hi, Currently the Linux virtio-crypto driver registers the crypto algorithm without verifying if the backend actually supports the algorithm. This kernel patch series adds support for registering algorithm with Linux crypto layer, only if the algorithm is supported by the backend device. This also makes the driver more compliant with the virtio-crypto spec [1]. I would appreciate any feedback or comments on this. Thank you Farhan Reference --------- [1] Virtio crypto spec proposal https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg00816.html Farhan Ali (2): crypto/virtio-crypto: Read crypto services and algorithm masks crypto/virtio-crypto: Register an algo only if it's supported drivers/crypto/virtio/virtio_crypto_algs.c | 110 ++++++++++++++++++--------- drivers/crypto/virtio/virtio_crypto_common.h | 25 +++++- drivers/crypto/virtio/virtio_crypto_core.c | 29 +++++++ drivers/crypto/virtio/virtio_crypto_mgr.c | 81 ++++++++++++++++++-- 4 files changed, 201 insertions(+), 44 deletions(-) -- 2.7.4
next reply other threads:[~2018-06-08 19:09 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-08 19:08 Farhan Ali [this message] 2018-06-08 19:08 ` [Qemu-devel] [RFC v1 0/2] Detect & register virtio-crypto algos only if it can be supported by backend Farhan Ali 2018-06-08 19:08 ` [RFC v1 1/2] crypto/virtio-crypto: Read crypto services and algorithm masks Farhan Ali 2018-06-08 19:08 ` [Qemu-devel] " Farhan Ali 2018-06-11 6:43 ` Gonglei (Arei) 2018-06-11 6:43 ` [Qemu-devel] " Gonglei (Arei) 2018-06-12 17:06 ` Farhan Ali 2018-06-12 17:06 ` [Qemu-devel] " Farhan Ali 2018-06-13 0:27 ` Gonglei (Arei) 2018-06-13 0:27 ` [Qemu-devel] " Gonglei (Arei) 2018-06-08 19:08 ` [RFC v1 2/2] crypto/virtio-crypto: Register an algo only if it's supported Farhan Ali 2018-06-08 19:08 ` [Qemu-devel] " Farhan Ali 2018-06-11 8:48 ` Gonglei (Arei) 2018-06-11 8:48 ` [Qemu-devel] " Gonglei (Arei) 2018-06-12 17:07 ` Farhan Ali 2018-06-12 17:07 ` [Qemu-devel] " Farhan Ali 2018-06-13 0:31 ` Gonglei (Arei) 2018-06-13 0:31 ` [Qemu-devel] " Gonglei (Arei)
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=cover.1528462918.git.alifm@linux.ibm.com \ --to=alifm@linux.ibm.com \ --cc=arei.gonglei@huawei.com \ --cc=borntraeger@de.ibm.com \ --cc=frankja@linux.ibm.com \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=longpeng2@huawei.com \ --cc=mst@redhat.com \ --cc=pasic@linux.ibm.com \ --cc=qemu-devel@nongnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.