Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org
Subject: Re: crypto_remove_spawns: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
Date: Wed, 17 Feb 2010 21:31:09 +0200	[thread overview]
Message-ID: <20100217193109.GB5256@x200> (raw)
In-Reply-To: <20100217003735.GB11975@gondor.apana.org.au>

On Wed, Feb 17, 2010 at 08:37:35AM +0800, Herbert Xu wrote:
> On Tue, Feb 16, 2010 at 09:31:39PM +0200, Alexey Dobriyan wrote:
> >
> > Which codepath exactly?
> 
> When a spawn is created the instance associated with it will have
> a zero-initialised cra_users entry.
> 
> > BTW, CBC or AES aren't used, just loaded.
> 
> Can you boot without aes/cbc loaded and see if it gets automatically
> loaded? PF_KEY users tend to load all possible algorithms when
> they start up.

AES and CBC are indeed loaded even if not used.

xfrm4_tunnel            1701  0
tunnel4                 2319  1 xfrm4_tunnel
ipcomp                  2063  0
xfrm_ipcomp             5154  1 ipcomp
xfrm4_mode_tunnel       1861  0
deflate                 2033  0
zlib_deflate           21231  1 deflate
zlib_inflate           18334  1 deflate
aes_generic            26652  0
des_generic            16263  0
cbc                     2945  0
sha1_generic            2223  0
md5                     4161  0
hmac                    3041  0
cryptomgr             105876  0
aead                    6474  1 cryptomgr
pcompress               1767  1 cryptomgr
crypto_null             2910  0
crypto_blkcipher       12080  3 cbc,cryptomgr,crypto_null
crypto_hash            15857  5
sha1_generic,md5,hmac,cryptomgr,crypto_null
crypto_algapi          16753  11
deflate,aes_generic,des_generic,cbc,hmac,cryptomgr,aead,pcompress,crypto_null,crypto_blkcipher,crypto_hash
af_key                 30024  0


Race started to become even less reproducible, so I can't confirm your patch quickly. :-(

  reply	other threads:[~2010-02-17 19:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 17:45 crypto_remove_spawns: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 Alexey Dobriyan
2010-02-15  5:27 ` Herbert Xu
2010-02-15  7:47   ` Alexey Dobriyan
2010-02-15  8:11     ` Herbert Xu
2010-02-15  8:14       ` Alexey Dobriyan
2010-02-16 12:02         ` Herbert Xu
2010-02-16 19:31           ` Alexey Dobriyan
2010-02-17  0:37             ` Herbert Xu
2010-02-17 19:31               ` Alexey Dobriyan [this message]
2010-02-18  0:26                 ` 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=20100217193109.GB5256@x200 \
    --to=adobriyan@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    /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