From: Binoy Jayan <binoy.jayan@linaro.org>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Oded <oded.golombek@arm.com>, Ofir <Ofir.Drang@arm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com, Shaohua Li <shli@kernel.org>,
linux-raid@vger.kernel.org, Rajendra <rnayak@codeaurora.org>,
Milan Broz <gmazyland@gmail.com>
Subject: Re: [RFC PATCH v3] crypto: Add IV generation algorithms
Date: Thu, 19 Jan 2017 20:33:50 +0530 [thread overview]
Message-ID: <CAHv-k_85e8d3_O50-DEynw=AXSfuFXfj4LT2cqVv2zqwMnG+Pw@mail.gmail.com> (raw)
In-Reply-To: <CAOtvUMenhgAuZXcsUPpOd5RfQh8XE9krve5YsFF3h-gK8KfDYQ@mail.gmail.com>
Hi Gilad,
On 19 January 2017 at 15:17, Gilad Ben-Yossef <gilad@benyossef.com> wrote:
> I tried adding sg_init_table() where I thought it was appropriate and
> it didn't resolve the issue.
>
> For what it's worth, my guess is that the difference between our
> setups is not related to Arm but to other options or the storage I'm
> using.
I was able to reproduce this again on my qemu setup with a 1GB virtual
disk. That is the same thing I do with the x86 setup as well.
> Are you using cryptd?
You mean config CRYPTO_CRYPTD?
-Binoy
prev parent reply other threads:[~2017-01-19 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 9:40 [RFC PATCH v3] IV Generation algorithms for dm-crypt Binoy Jayan
2017-01-18 9:40 ` [RFC PATCH v3] crypto: Add IV generation algorithms Binoy Jayan
2017-01-18 15:21 ` Gilad Ben-Yossef
2017-01-19 4:42 ` Binoy Jayan
2017-01-19 9:47 ` Gilad Ben-Yossef
2017-01-19 15:03 ` Binoy Jayan [this message]
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='CAHv-k_85e8d3_O50-DEynw=AXSfuFXfj4LT2cqVv2zqwMnG+Pw@mail.gmail.com' \
--to=binoy.jayan@linaro.org \
--cc=Ofir.Drang@arm.com \
--cc=agk@redhat.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=gilad@benyossef.com \
--cc=gmazyland@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=oded.golombek@arm.com \
--cc=rnayak@codeaurora.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).