linux-kernel - Re: Possible mem leak in copy

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]

Message-Id: <200804170617.36010.arnd@arndb.de>
Date:	Thu, 17 Apr 2008 06:17:34 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Jesper Juhl <jesper.juhl@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: Possible mem leak in copy_process()

On Wednesday 16 April 2008, Jesper Juhl wrote:
> 
> Perhaps it can never happen the way Coverity thinks it can. You are a much 
> better judge of that than I, but it looks to me like it's at least 
> possible in theory - in which case we have a potential leak every time we 
> create a new process and that can't be good...

I think you're just looking at the common case here, which is correct:
The pid is allocated for task creation and stays around as long as the
task does. It gets freed when the last reference to it goes away,
usually in the put_pid() called from exit().

	Arnd <><
--
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/