Re: [PATCH 1/2] crypto: fix crypto_alloc_{tfm,base}() return value

On Mon, Oct 09, 2006 at 09:14:46PM +1000, Herbert Xu wrote:

> Actually, crypto_alloc_tfm is an obsolete function which is supposed
> to maintain its previous semantics of returning NULL or success.

I misunderstood about crypto_alloc_tfm().

BTW, ecryptfs and reiser4 are still using crypto_alloc_tfm().
Should we mark it as __deprecated?

> I don't quite see where the problem with crypto_alloc_base is.

- __crypto_alloc_tfm() should return -ENOMEM on kzalloc() failure.
  But it returns NULL.

- crypto_alloc_base() may not return -EINTR on signal_pending()

I'll fix the patch and resend with more clear description later.

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

---

• Follow-Ups:
  • Re: [PATCH 1/2] crypto: fix crypto_alloc_{tfm,base}() return value
    • From: Herbert Xu <[email protected]>

• References:
  • [PATCH 1/2] crypto: fix crypto_alloc_{tfm,base}() return value
    • From: [email protected] (Akinobu Mita)
  • Re: [PATCH 1/2] crypto: fix crypto_alloc_{tfm,base}() return value
    • From: Herbert Xu <[email protected]>

• Prev by Date: Re: User switchable HW mappings & cie
• Next by Date: Re: [PATCH] lockdep: annotate nfs/nfsd in-kernel sockets
• Previous by thread: Re: [PATCH 1/2] crypto: fix crypto_alloc_{tfm,base}() return value
• Next by thread: Re: [PATCH 1/2] crypto: fix crypto_alloc_{tfm,base}() return value
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]