linux-kernel - Re: [PATCH 1/1] added code to export CAP_LAST_CAP in /proc/sys/kernel modeled after ngroups

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: <20111014135122.4bb95565.akpm@linux-foundation.org>
Date:	Fri, 14 Oct 2011 13:51:22 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Dan Ballard <dan@...dstab.net>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Lennart Poettering <lennart@...ttering.net>,
	Kay Sievers <kay.sievers@...y.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] added code to export CAP_LAST_CAP in
 /proc/sys/kernel modeled after ngroups_max

On Wed, 12 Oct 2011 15:56:34 -0700
Dan Ballard <dan@...dstab.net> wrote:

> In response to a request by the Linux Plumbers about getting CAP_LAST_CAP exposed somehow, I talked to Lennart Poettering briefly and went ahead and added cap_last_cap to /proc/sys/kernel in a similar fashion as ngroups_max is exported.  The patch is simple and just adds another struct to the array of exported values in sysctl.c.
> 

The changelog should explain the reason for making this change, please.
People aren't going to remember some vague email thread five years
from now.

Also, please update the documentation.  Documentation/sysctl/kernel.txt
is a suitable place.  Lots of things in kern_table[] are undocumented,
but that's not a reason for the rest of us to suck as much as sched
developers :)

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