From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: mst@redhat.com, jasowang@redhat.com, arei.gonglei@huawei.com,
herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: [BUG] skcipher: Test 1 failed (invalid result) on encryption for cts(virtio_crypto_aes_cbc)
Date: Thu, 18 Jan 2018 10:08:04 +0100 [thread overview]
Message-ID: <20180118090804.GB1988@Red> (raw)
Hello
When modprobing tcrypt on a qemu virtual machine, I get the following trace in dmesg:
skcipher: Test 1 failed (invalid result) on encryption for cts(virtio_crypto_aes_cbc)
Regards
Corentin Labbe
WARNING: multiple messages have this Message-ID (diff)
From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: mst@redhat.com, jasowang@redhat.com, arei.gonglei@huawei.com,
herbert@gondor.apana.org.au, davem@davemloft.net
Cc: virtualization@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [BUG] skcipher: Test 1 failed (invalid result) on encryption for cts(virtio_crypto_aes_cbc)
Date: Thu, 18 Jan 2018 10:08:04 +0100 [thread overview]
Message-ID: <20180118090804.GB1988@Red> (raw)
Hello
When modprobing tcrypt on a qemu virtual machine, I get the following trace in dmesg:
skcipher: Test 1 failed (invalid result) on encryption for cts(virtio_crypto_aes_cbc)
Regards
Corentin Labbe
next reply other threads:[~2018-01-18 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 9:08 Corentin Labbe [this message]
2018-01-18 9:08 ` [BUG] skcipher: Test 1 failed (invalid result) on encryption for cts(virtio_crypto_aes_cbc) Corentin Labbe
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=20180118090804.GB1988@Red \
--to=clabbe.montjoie@gmail.com \
--cc=arei.gonglei@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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 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.