From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Farhan Ali <alifm@linux.ibm.com>,
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,
Jason Wang <jasowang@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH v2 0/2] Detect & register virtio-crypto algos only if it can be supported by backend
Date: Tue, 19 Jun 2018 16:08:05 +0200 [thread overview]
Message-ID: <0c5d7e42-e6c5-6aa2-8c1b-487c8cc9eb21@de.ibm.com> (raw)
In-Reply-To: <44ccc5db-e1d4-27b7-8942-c77f467f422e@linux.ibm.com>
On 06/19/2018 03:26 PM, Farhan Ali wrote:
> A polite ping :)
>
> If no one has any more comments/feedback then I would like to how to merge these patches to the mainline kernel tree.
I think it should go via Michael Tsirkin or Jason Wang (Adding Jason).
Also adding Herbert Xu as FYI.
I have not looked into the details of the patch, but I like the idea.
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> Thanks
> Farhan
>
> On 06/13/2018 04:38 PM, Farhan Ali wrote:
>> 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
>>
>> ChangeLog
>> ---------
>> v1 -> v2
>> - Modify comment as suggested by Arei (patch 1)
>> - Modify error message as suggested by Arei (patch 2)
>>
>>
>> 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 | 112 ++++++++++++++++++---------
>> 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, 202 insertions(+), 45 deletions(-)
>>
>
next prev parent reply other threads:[~2018-06-19 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 20:38 Farhan Ali
2018-06-13 20:38 ` [PATCH v2 1/2] crypto/virtio-crypto: Read crypto services and algorithm masks Farhan Ali
2018-06-13 20:38 ` [PATCH v2 2/2] crypto/virtio-crypto: Register an algo only if it's supported Farhan Ali
2018-06-19 13:26 ` [PATCH v2 0/2] Detect & register virtio-crypto algos only if it can be supported by backend Farhan Ali
2018-06-19 14:08 ` Christian Borntraeger [this message]
2018-06-19 14:32 ` Herbert Xu
2018-06-19 14:57 ` Farhan Ali
2018-06-19 15:30 ` Michael S. Tsirkin
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=0c5d7e42-e6c5-6aa2-8c1b-487c8cc9eb21@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=arei.gonglei@huawei.com \
--cc=frankja@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®