linux-kernel - Re: [PATCH] Fix for binary

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] [day] [month] [year] [list]

Message-ID: <CANN689GLCsHTf09Rf43MAitQdTkUcd3ykhoZgk86eQzE_PnXzg@mail.gmail.com>
Date:	Sat, 17 Dec 2011 17:23:25 -0800
From:	Michel Lespinasse <walken@...gle.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Christoph Hellwig <hch@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix for binary_sysctl() memory leak

On Sat, Dec 17, 2011 at 2:14 PM, Eric W. Biederman
<ebiederm@...ssion.com> wrote:
> Calling sysctl(2) is very rare.  I don't know if it actually happens
> anywhere with a modern userspace except in regression tests.
> Effectively we retain sysctl(2) because it doesn't take too much to
> maintain.

Agree, there is no good reason one would call sysctl() anymore.

> Michel what caused you to discover this bug?  If you are using
> sysctl(2) in production code I am a bit worried.

Well, somebody hit it :) To be honest, I'm not sure how they came to
do that. It wasn't in a datacenter setting.

-- 
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
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/