From: Herbert Xu <herbert@gondor.apana.org.au>
To: Nathan Royce <nroycea+kernel@gmail.com>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: XTS Crypto Not Found In /proc/crypto Even After Compiled for 4.10.1.
Date: Fri, 3 Mar 2017 20:04:32 +0800 [thread overview]
Message-ID: <20170303120432.GA26540@gondor.apana.org.au> (raw)
In-Reply-To: <CALaQ_hoafES-K1ds-XUPC6h4VnHX_ebym4LYjeuq1jHdbLYuDQ@mail.gmail.com>
On Fri, Mar 03, 2017 at 04:36:18AM -0600, Nathan Royce wrote:
> I do have ECB selected as well:
> DM_CRYPT=y
> CRYPTO_ECB=y
> CRYPTO_XTS=y
>
> name : ecb(aes)
> driver : ecb-aes-s5p
> module : kernel
> priority : 100
> refcnt : 1
> selftest : passed
> internal : no
> type : ablkcipher
> async : yes
> blocksize : 16
> min keysize : 16
> max keysize : 32
> ivsize : 0
> geniv : <default>
> //still no "xts" can be found in the list
Weird. So you can't find any instances of xts in /proc/crypto
at all? Even if the self-test fails it should still register an
entry there...
In any case, I think disabling the s5p driver should work at
least.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2017-03-03 12:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 10:36 XTS Crypto Not Found In /proc/crypto Even After Compiled for 4.10.1 Nathan Royce
2017-03-03 12:04 ` Herbert Xu [this message]
2017-03-03 14:08 ` Nathan Royce
-- strict thread matches above, loose matches on Subject: below --
2017-03-06 16:18 Nathan Royce
2017-03-06 17:35 ` Krzysztof Kozlowski
2017-03-06 21:29 ` Nathan Royce
2017-03-08 17:45 ` Krzysztof Kozlowski
2017-03-08 21:15 ` Krzysztof Kozlowski
2017-03-09 11:16 ` Nathan Royce
2017-03-10 18:06 ` Krzysztof Kozlowski
2017-03-10 21:44 ` Nathan Royce
2017-03-12 19:13 ` Krzysztof Kozlowski
2017-03-13 17:06 ` Krzysztof Kozlowski
2017-03-14 9:20 ` Herbert Xu
2017-04-06 9:54 ` Herbert Xu
2017-04-08 2:02 ` Herbert Xu
2017-04-08 12:23 ` Krzysztof Kozlowski
[not found] <CALaQ_hoZ6wh-H_NNoT80r6kthvFpL05zNWr7upVqispknXMEvg@mail.gmail.com>
2017-03-03 4:02 ` Herbert Xu
2017-03-03 9:00 ` Nathan Royce
2017-03-03 9:33 ` Herbert Xu
2017-03-05 17:16 ` Krzysztof Kozlowski
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=20170303120432.GA26540@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=k.kozlowski@samsung.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nroycea+kernel@gmail.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).