Re: Hopefully, kmalloc() will always succeed, but if it doesn't then....

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Amit Choudhary" <[email protected]>
Subject: Re: Hopefully, kmalloc() will always succeed, but if it doesn't then....
From: "Pekka Enberg" <[email protected]>
Date: Sun, 22 Oct 2006 23:22:59 +0300
Cc: [email protected]
In-reply-to: <[email protected]>
References: <[email protected]>
Sender: [email protected]

On 10/22/06, Amit Choudhary <[email protected]> wrote:

So, if memory allocation to 'a' fails, it is going to kfree 'b'. But since 'b'
is not initialized, kfree may crash (unless DEBUG is defined).

I have seen the same case at many places when allocating in a loop.


So you found a bug. Why not send a patch to fix it?
-
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: Hopefully, kmalloc() will always succeed, but if it doesn't then....
  - From: Amit Choudhary <[email protected]>
- Re: Hopefully, kmalloc() will always succeed, but if it doesn't then....
  - From: Jan Engelhardt <[email protected]>

References:
- Hopefully, kmalloc() will always succeed, but if it doesn't then....
  - From: Amit Choudhary <[email protected]>

Prev by Date: Re: Strange errors from e1000 driver (2.6.18)
Next by Date: 2.6.19-rc2-git7 shutdown problem
Previous by thread: Hopefully, kmalloc() will always succeed, but if it doesn't then....
Next by thread: Re: Hopefully, kmalloc() will always succeed, but if it doesn't then....
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]

Powered by Linux