On Tue, Feb 16, 2010 at 08:02:03PM +0800, Herbert Xu wrote:
> On Mon, Feb 15, 2010 at 10:14:08AM +0200, Alexey Dobriyan wrote:
> >
> > Yes, ipcomp bug triggers almost immediately.
> > Anyway, this is just description of what I do.
>
> Can you see if this patch makes it go away?
>
> This can happen when you're unloading aes just as an algorithm
> that uses aes (such as cbc(aes)) is being created.
Which codepath exactly?
I'd say try_module_get() should fail somewhere.
BTW, CBC or AES aren't used, just loaded.
Here is setkey script:
#!/usr/sbin/setkey -f
flush;
spdflush;
add A B ipcomp 44 -m tunnel -C deflate;
add B A ipcomp 45 -m tunnel -C deflate;
spdadd A B any -P in ipsec
ipcomp/tunnel/192.168.1.2-192.168.1.3/use;
spdadd B A any -P out ipsec
ipcomp/tunnel/192.168.1.3-192.168.1.2/use;
> --- a/crypto/algapi.c
> +++ b/crypto/algapi.c
> @@ -165,6 +165,8 @@ static void crypto_remove_spawns(struct crypto_alg *alg,
>
> spawn->alg = NULL;
> spawns = &inst->alg.cra_users;
> + if (!spawns->next)
> + break;
> }
> } while ((spawns = crypto_more_spawns(alg, &stack, &top,
> &secondary_spawns)));
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
