Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.

Hi!

> > I decided to keep it simple. If someone is calling kfree_nullify() with anything other than a
> > simple variable, then they should call kfree().
> 
> kfree_nullify() has to replace kfree() to be of any use one day. So this is not an option.
> 

Doing kfree() that writes to its argument is not an option. kfree()
looks like a function, so it should behave as one. KFREE() might be
okay.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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:
- Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
  - From: Amit Choudhary <[email protected]>
- Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
  - From: Ingo Oeser <[email protected]>

Prev by Date: Re: [PATCH] Open Firmware device tree virtual filesystem
Next by Date: Re: [PATCH] preliminary sata_promise ATAPI support
Previous by thread: Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
Next by thread: Re: [patch] remove MAX_ARG_PAGES
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]