linux-kernel - Re: [PATCH] filesystems: use has_capability_noaudit interface for reserved blocks checks

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: <20081113230717.GA25117@mit.edu>
Date:	Thu, 13 Nov 2008 18:07:17 -0500
From:	Theodore Tso <tytso@....edu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
	sct@...hat.com, adilger@....com, linux-ext4@...r.kernel.org,
	dedekind@...radead.org, ext-adrian.hunter@...ia.com,
	linux-mtd@...ts.infradead.org, dushistov@...l.ru, jmorris@...ei.org
Subject: Re: [PATCH] filesystems: use has_capability_noaudit interface for
	reserved blocks checks

On Thu, Nov 13, 2008 at 02:53:16PM -0800, Andrew Morton wrote:
> On Tue, 11 Nov 2008 14:12:49 -0500
> Eric Paris <eparis@...hat.com> wrote:
> 
> > ext[2,3,4], ufs, and ubifs all check for  CAP_SYS_RESOURCE to determine
> > if they should allow reserved blocks to be used.  A process not having
> > this capability is not failing some security decision and should not be
> > audited.  Thus move to using has_capability_noaudit.
> > 
> > Signed-off-by: Eric Paris <eparis@...hat.com>
> > ---
> > 
> > I would like to push this patch through the security tree (since that's
> > the only place the new cap_noaudit interface exists), but I'd like to
> > get an ACK from each subsystem maintainer.

For ext4:

Acked-by: "Theodore Ts'o" <tytso@....edu>

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