Re: [PATCH]crypto: Fix algorithm and driver duplicate registered

[Youquan,Song]

> Can you show me a sample /proc/crypto showing this problem and how
> you created it?
> 
Sorry for late. I use the cryptodev-2.6 tree, enable AESNI and PCLMULQDQ NI.

Step: like this.  
A. modprobe tcrypt mode=35
B. modprobe aesni-intel
C. modprobe tcrypt mode=35

After I do A. Because it do not load aesni-intel, so I do B, then repeat C.

cat /proc/crypto.

there is two identical gcm: 

name         : gcm(aes)
driver       : gcm_base(ctr-aes-aesni,ghash-clmulni)
module       : gcm
priority     : 400
refcnt       : 1
selftest     : unknown
type         : aead
async        : yes
blocksize    : 1
ivsize       : 16
maxauthsize  : 16
geniv        : <built-in>

name         : gcm(aes)
driver       : gcm_base(ctr-aes-aesni,ghash-clmulni)
module       : gcm
priority     : 400
refcnt       : 1
selftest     : unknown
type         : aead
async        : yes
blocksize    : 1
ivsize       : 16
maxauthsize  : 16
geniv        : <built-in>

name         : fpu(ctr(__aes-aesni))
driver       : cryptd(fpu(ctr(__driver-aes-aesni)))
module       : cryptd
priority     : 50
refcnt       : 1
selftest     : passed
type         : ablkcipher
async        : yes
blocksize    : 1
min keysize  : 16
max keysize  : 32
ivsize       : 16
geniv        : <default>

name         : fpu(ctr(__aes-aesni))
driver       : fpu(ctr(__driver-aes-aesni))
module       : fpu
priority     : 0
refcnt       : 1
selftest     : passed
type         : blkcipher
blocksize    : 1
min keysize  : 16
max keysize  : 32
ivsize       : 16

 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/