Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946852Ab2ERXJX (ORCPT ); Fri, 18 May 2012 19:09:23 -0400 Received: from mga09.intel.com ([134.134.136.24]:62470 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946814Ab2ERXJS (ORCPT ); Fri, 18 May 2012 19:09:18 -0400 MIME-Version: 1.0 In-Reply-To: References: <1337284200-1838-1-git-send-email-auke-jan.h.kok@intel.com> Date: Fri, 18 May 2012 16:09:15 -0700 Message-ID: Subject: Re: [PATCH] Trace event for capable(). From: "Kok, Auke-jan H" To: richard -rw- weinberger Cc: Serge Hallyn , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Eric Paris Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1186 Lines: 29 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. 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/