linux-kernel - Re: [rfc 3/3] prctl: Add PR_SET_MM codes to tune up mm

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: <20111208073043.GX21678@moon>
Date:	Thu, 8 Dec 2011 11:30:43 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
	Tejun Heo <tj@...nel.org>, Andrew Vagin <avagin@...nvz.org>,
	Serge Hallyn <serge.hallyn@...onical.com>,
	Pavel Emelyanov <xemul@...allels.com>,
	Vasiliy Kulikov <segoon@...nwall.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Michael Kerrisk <mtk.manpages@...il.com>
Subject: Re: [rfc 3/3] prctl: Add PR_SET_MM codes to tune up mm_struct entires

On Wed, Dec 07, 2011 at 11:15:12PM -0800, Andrew Morton wrote:
> On Thu, 8 Dec 2011 11:07:24 +0400 Cyrill Gorcunov <gorcunov@...il.com> wrote:
> 
> > > 
> > > The prctl(2) manpage will need to be updated.  Please Cc Michael on all
> > > such changes.
> > >
> > 
> > you mean -- Michael Kerrisk, mtk AT man7.org, right?
> 
> That isn't what ./MAINTAINERS says?
> 

OK, I've just found him in MAINTAINERS.

> > > 
> > > This is starting to add a non-trivial amount of code.  Perhaps we need
> > > to introduce a Kconfig variable to control such things as this, to
> > > prevent bloating up kernels which aren't require to support c/r?
> > > 
> > 
> > Dunno, Andrew. Actually I agreed that these snippets are mostly
> > needed for c/r only, but the initial idea over all changes was
> > to add levers into kernel which might be helpful not only
> > for c/r but for someone else as well.
> 
> In each instance, a case would need to be made for that.  Plus if
> people later come along who want access to these things for other
> purposes, they can send a patch!
> 
> There will always be people who would *prefer* that this material not
> be present in their vmlinux.  For those people, this patch is a
> regression!
> 

OK, I'll add some Kconfing variable for that. Lets see how it goes.

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