Re: [PATCH] ecryptfs: bad allocation result check

On Fri, Nov 03, 2006 at 02:51:22PM -0500, Florin Malita wrote:
> The kmalloc() result in* *ecryptfs_crypto_api_algify_cipher_name()
> is assigned to an indirectly referenced pointer and not to the
> pointer itself, so the current result check is incorrect.

Thanks; this bug was already caught and fixed.
-
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/

---

• References:
  • [PATCH] ecryptfs: bad allocation result check
    • From: Florin Malita <[email protected]>

• Prev by Date: [GIT PATCH] USB fixes for 2.6.18-rc4
• Next by Date: Re: unregister_netdevice: waiting for eth0 to become free
• Previous by thread: [PATCH] ecryptfs: bad allocation result check
• Next by thread: [GIT PATCH] PCI fixes for 2.6.19-rc4
• 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]