2007-10-16 17:56:39

by Krzysztof Oledzki

[permalink] [raw]
Subject: Truncated(?) /proc/crypto on x86_64 on 2.6.22

Hello,

After switching from i386 to x86_64 I noticed that /proc/crypto is much
shorter:

# wc -l /proc/crypto crypto-64
482 /proc/crypto
349 crypto-64

# diff -Nur /proc/crypto crypto-64
--- /proc/crypto 2007-10-16 19:49:45.110694374 +0200
+++ crypto-64 2007-10-16 19:48:10.000000000 +0200
@@ -1,136 +1,3 @@
-name : cbc(twofish)
-driver : cbc(twofish-i586)
-module : kernel
-priority : 200
-refcnt : 1
-type : blkcipher
-blocksize : 16
-min keysize : 16
-max keysize : 32
-ivsize : 16
-
-name : cbc(camellia)
-driver : cbc(camellia-generic)
-module : kernel
-priority : 100
-refcnt : 1
-type : blkcipher
-blocksize : 16
-min keysize : 16
-max keysize : 32
-ivsize : 16
-
-name : cbc(serpent)
-driver : cbc(serpent-generic)
-module : kernel
-priority : 0
-refcnt : 1
-type : blkcipher
-blocksize : 16
-min keysize : 0
-max keysize : 32
-ivsize : 16
-
-name : cbc(aes)
-driver : cbc(aes-i586)
-module : kernel
-priority : 200
-refcnt : 2467
-type : blkcipher
-blocksize : 16
-min keysize : 16
-max keysize : 32
-ivsize : 16
-
-name : cbc(blowfish)
-driver : cbc(blowfish-generic)
-module : kernel
-priority : 0
-refcnt : 1
-type : blkcipher
-blocksize : 8
-min keysize : 4
-max keysize : 56
-ivsize : 8
-
-name : cbc(des3_ede)
-driver : cbc(des3_ede-generic)
-module : kernel
-priority : 0
-refcnt : 1147
-type : blkcipher
-blocksize : 8
-min keysize : 24
-max keysize : 24
-ivsize : 8
-
-name : cbc(des)
-driver : cbc(des-generic)
-module : kernel
-priority : 0
-refcnt : 1
-type : blkcipher
-blocksize : 8
-min keysize : 8
-max keysize : 8
-ivsize : 8
-
-name : ecb(cipher_null)
-driver : ecb(cipher_null-generic)
-module : kernel
-priority : 0
-refcnt : 1
-type : blkcipher
-blocksize : 1
-min keysize : 0
-max keysize : 0
-ivsize : 0
-
-name : xcbc(aes)
-driver : xcbc(aes-i586)
-module : kernel
-priority : 200
-refcnt : 1
-type : hash
-blocksize : 16
-digestsize : 16
-
-name : hmac(sha256)
-driver : hmac(sha256-generic)
-module : kernel
-priority : 0
-refcnt : 1
-type : hash
-blocksize : 64
-digestsize : 32
-
-name : hmac(sha1)
-driver : hmac(sha1-generic)
-module : kernel
-priority : 0
-refcnt : 3613
-type : hash
-blocksize : 64
-digestsize : 20
-
-name : hmac(md5)
-driver : hmac(md5-generic)
-module : kernel
-priority : 0
-refcnt : 1
-type : hash
-blocksize : 64
-digestsize : 16
-
-name : hmac(digest_null)
-driver : hmac(digest_null-generic)
-module : kernel
-priority : 0
-refcnt : 1
-type : hash
-blocksize : 1
-digestsize : 0
-
name : crc32c
driver : crc32c-generic
module : kernel
@@ -310,7 +177,7 @@
driver : des3_ede-generic
module : kernel
priority : 0
-refcnt : 1147
+refcnt : 1
type : cipher
blocksize : 8
min keysize : 24
@@ -411,7 +278,7 @@
driver : sha1-generic
module : kernel
priority : 0
-refcnt : 3613
+refcnt : 1
type : digest
blocksize : 64
digestsize : 20
@@ -461,7 +328,7 @@
max keysize : 0

name : twofish
-driver : twofish-i586
+driver : twofish-x86_64
module : kernel
priority : 200
refcnt : 1
@@ -471,10 +338,10 @@
max keysize : 32

name : aes
-driver : aes-i586
+driver : aes-x86_64
module : kernel
priority : 200
-refcnt : 2467
+refcnt : 1
type : cipher
blocksize : 16
min keysize : 16


# grep CRYPT .config
CONFIG_BLK_DEV_CRYPTOLOOP=y
CONFIG_DM_CRYPT=y
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ABLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_WP512=y
CONFIG_CRYPTO_TGR192=y
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_PCBC=y
CONFIG_CRYPTO_LRW=y
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_FCRYPT=y
CONFIG_CRYPTO_BLOWFISH=y
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_TWOFISH_COMMON=y
CONFIG_CRYPTO_TWOFISH_X86_64=y
CONFIG_CRYPTO_SERPENT=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=y
CONFIG_CRYPTO_CAST5=y
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_TEA=y
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_KHAZAD=y
CONFIG_CRYPTO_ANUBIS=y
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_MICHAEL_MIC=y
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CAMELLIA=y

Is it normall?

Best regards,

Krzysztof Ol?dzki


Subject: Re: Truncated(?) /proc/crypto on x86_64 on 2.6.22

* Krzysztof Oledzki | 2007-10-16 19:56:33 [+0200]:

> After switching from i386 to x86_64 I noticed that /proc/crypto is much
> shorter:
>
> # wc -l /proc/crypto crypto-64
> 482 /proc/crypto
> 349 crypto-64
>

It is all fine from what I can see in this diff.


> # diff -Nur /proc/crypto crypto-64
> --- /proc/crypto 2007-10-16 19:49:45.110694374 +0200
> +++ crypto-64 2007-10-16 19:48:10.000000000 +0200
> @@ -1,136 +1,3 @@
> -name : cbc(twofish)
> -driver : cbc(twofish-i586)
> -module : kernel
> -priority : 200
> -refcnt : 1
> -type : blkcipher
> -blocksize : 16
> -min keysize : 16
> -max keysize : 32
> -ivsize : 16
> -

This algo is stacked, because it was used. You have probably one output
after 'modprobe tcrypt' and the other before :)

Sebastian

2007-10-18 15:19:51

by Krzysztof Oledzki

[permalink] [raw]
Subject: Re: Truncated(?) /proc/crypto on x86_64 on 2.6.22



On Tue, 16 Oct 2007, Sebastian Siewior wrote:

> * Krzysztof Oledzki | 2007-10-16 19:56:33 [+0200]:
>
>> After switching from i386 to x86_64 I noticed that /proc/crypto is much
>> shorter:
>>
>> # wc -l /proc/crypto crypto-64
>> 482 /proc/crypto
>> 349 crypto-64
>>
>
> It is all fine from what I can see in this diff.
>
>
>> # diff -Nur /proc/crypto crypto-64
>> --- /proc/crypto 2007-10-16 19:49:45.110694374 +0200
>> +++ crypto-64 2007-10-16 19:48:10.000000000 +0200
>> @@ -1,136 +1,3 @@
>> -name : cbc(twofish)
>> -driver : cbc(twofish-i586)
>> -module : kernel
>> -priority : 200
>> -refcnt : 1
>> -type : blkcipher
>> -blocksize : 16
>> -min keysize : 16
>> -max keysize : 32
>> -ivsize : 16
>> -
>
> This algo is stacked, because it was used. You have probably one output
> after 'modprobe tcrypt' and the other before :)

Right. The other (bigger) output is after starting IPSec. Sorry for the
noise and thank you for the explanation.

Best regards,

Krzusztof Ol?dzki