The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Youquan,Song" <youquan.song@linux.intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Youquan,Song" <youquan.song@linux.intel.com>,
	linux-kernel@vger.kernel.org, ying.huang@intel.com,
	kent.liu@intel.com, youquan.song@intel.com
Subject: Re: [PATCH]crypto: Fix algorithm and driver duplicate registered
Date: Mon, 23 Nov 2009 12:21:17 -0500	[thread overview]
Message-ID: <20091123172117.GA14372@youquan-linux.bj.intel.com> (raw)
In-Reply-To: <20091119114730.GC6392@gondor.apana.org.au>

> 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

 


  reply	other threads:[~2009-11-23  9:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19  0:32 [PATCH]crypto: Fix algorithm and driver duplicate registered Youquan,Song
2009-11-19  0:18 ` Herbert Xu
2009-11-19 11:02   ` Youquan,Song
2009-11-19 11:47     ` Herbert Xu
2009-11-23 17:21       ` Youquan,Song [this message]
2009-11-23 10:52         ` Herbert Xu
2009-11-23 17:47       ` Youquan,Song
2009-11-23 11:31         ` Herbert Xu
2009-11-25 10:35           ` Youquan,Song
2009-11-25  3:12             ` Herbert Xu

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=20091123172117.GA14372@youquan-linux.bj.intel.com \
    --to=youquan.song@linux.intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kent.liu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.com \
    --cc=youquan.song@intel.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