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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 1 Jan 2007 19:36:41 +0100
From:	Pavel Machek <pavel@....cz>
To:	Ingo Oeser <ioe-lkml@...eria.de>
Cc:	Amit Choudhary <amit2030@...oo.com>,
	Bernd Petrovitsch <bernd@...mix.at>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/