Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967025Ab2ERXTx (ORCPT ); Fri, 18 May 2012 19:19:53 -0400 Received: from 50-56-35-84.static.cloud-ips.com ([50.56.35.84]:43422 "EHLO mail.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756140Ab2ERXTt (ORCPT ); Fri, 18 May 2012 19:19:49 -0400 From: Serge Hallyn Reply-To: Serge Hallyn To: "Kok, Auke-jan H" , richard -rw- weinberger Cc: Serge Hallyn , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Eric Paris Subject: Re: [PATCH] Trace event for capable(). X-Mailer: Modest 3.2 References: <1337284200-1838-1-git-send-email-auke-jan.h.kok@intel.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-ID: <1337383163.1463.1.camel@Nokia-N900-51-1> Date: Fri, 18 May 2012 18:19:23 -0500 Message-Id: <1337383163.1463.2.camel@Nokia-N900-51-1> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1833 Lines: 42 ----- Original message ----- > On Fri, May 18, 2012 at 3:33 PM, richard -rw- weinberger > wrote: > > > > On Thu, May 17, 2012 at 9:50 PM, Auke Kok > > wrote: > > > Add a simple trace event for capable(). > > > > > > There's been a lot of discussion around capable(), and there > > > are plenty of tools to help reduce capabilities' usage from > > > userspace. A major gap however is that it's almost impossible > > > to see or verify which bits are requested from either userspace > > > or in the kernel. > > > > > > This patch adds a minimal tracer that will print out which > > > CAPs are requested and whether the request was granted. > > > > Can we please have support for user namespaces? > > At least idicate whether the current namespace is init_user_ns or not. > > that was the main reason for sending this out already - that should be > trivial to add to the trace event, but I haven't looked at namespaces > yet myself. I'll check it out. > right, trivial to add, but either go through linux-next or wait for Eric's patchset to move from there to Linus' tree. Print the from_kuid(&init_user_ns, current_uid()), and if not in init_user_ns then also print the ns creator and task uid in his own ns. I don't think you need to do that right now. > Auke > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" > in the body of a message to majordomo@vger.kernel.org > More majordomo info at  http://vger.kernel.org/majordomo-info.html > Please read the FAQ at  http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/