From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D051DC433E3 for ; Tue, 28 Jul 2020 16:20:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AD3AC2074F for ; Tue, 28 Jul 2020 16:20:18 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=paul-moore-com.20150623.gappssmtp.com header.i=@paul-moore-com.20150623.gappssmtp.com header.b="X9zkASWi" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731078AbgG1QUS (ORCPT ); Tue, 28 Jul 2020 12:20:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52804 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730679AbgG1QUR (ORCPT ); Tue, 28 Jul 2020 12:20:17 -0400 Received: from mail-ed1-x543.google.com (mail-ed1-x543.google.com [IPv6:2a00:1450:4864:20::543]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 330DFC061794 for ; Tue, 28 Jul 2020 09:20:17 -0700 (PDT) Received: by mail-ed1-x543.google.com with SMTP id i26so11933363edv.4 for ; Tue, 28 Jul 2020 09:20:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paul-moore-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=JdZsT2eGwbAuU6cqrvpHfhhr/C0FiXQpjb+sn/9k/nA=; b=X9zkASWiHWpjw6+nfqculWmMqamRYe3jn+QpljCcE6rJCor63DWmNH8UXkREdL4LmA hX7JihkSmaISC2e90syV/nPflCE7AL7AEZ1Z+4EgWTRwS6F1oltQA5o7sllAVXXTtOjA tnNZaCWpLrx7cGQ4mcDqtAG5KnT7R9u8iYrT+7Wbanfa6AWhKysZe2sNE10Y9rEP3biP LvBFRmYStOgbfPGCMZ9tS3Prfl6Thygrao4u+wwHdIjNPHXgO0nNBDY8S2hpJIHWjH81 RrqgQqigk8TbQaqyAGa5fi6b8NtKy46FAuTe4A877W2VO7H7x39HZK+YYKmAzGAmrUI5 2vhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=JdZsT2eGwbAuU6cqrvpHfhhr/C0FiXQpjb+sn/9k/nA=; b=YHjZX18eTVQOwf13sZQZlbvahr21w4jxMPyCVhQlJ8KG5CLNn0OqmZkJMNXYWQL1zO 0DvFV6B+2HbCQBDrmU6wRbIbEXuiQRSAw/q+fGpzYXGgj+sBQ8v554jp8YgTuzY1C7ws nIj3kIJCRTf7c656f5/Hl7aG1x8eblEspFevVGay+vwR7/0KBCpaClRSpq22dfcz+81t /mvg26vRptEBlXslMyJ/Ub9MmscoYropeGyprSQd7H2l4359eYN3hd6beIXkNv4DCSl1 KB5Lz3T+AlncmYBNWLEq9tBrWgM87zRek8t9v2gnhhdIrKdnRk5Av0xzmtEGiO2RsrPD DsIQ== X-Gm-Message-State: AOAM531BSaUL28RqXuinaUJWU75X6tycmmUM3vENuHxz3P8c5z6112y5 x1Ph0I6hysGNAxgDH6cErXdY01Jltu42dI4gZVVS X-Google-Smtp-Source: ABdhPJzz74dgHHHep+KqO57RY1mJjew1iG0Rr5CUV4iYLH0RYRsPHpC3OsJhrBq7IcV6icvPjOOe0+CBPJ68RFWRx0Y= X-Received: by 2002:aa7:db10:: with SMTP id t16mr13033990eds.196.1595953215861; Tue, 28 Jul 2020 09:20:15 -0700 (PDT) MIME-Version: 1.0 References: <20200724091520.880211-1-tweek@google.com> In-Reply-To: From: Paul Moore Date: Tue, 28 Jul 2020 12:20:04 -0400 Message-ID: Subject: Re: [PATCH] selinux: add tracepoint on denials To: =?UTF-8?Q?Thi=C3=A9baud_Weksteen?= Cc: Steven Rostedt , Stephen Smalley , Nick Kralevich , Joel Fernandes , Eric Paris , Ingo Molnar , Mauro Carvalho Chehab , "David S. Miller" , Rob Herring , linux-kernel , SElinux list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 28, 2020 at 12:02 PM Thi=C3=A9baud Weksteen = wrote: > On Tue, Jul 28, 2020 at 5:12 PM Paul Moore wrote: > > Perhaps it would be helpful if you provided an example of how one > > would be expected to use this new tracepoint? That would help put > > things in the proper perspective. > > The best example is the one I provided in the commit message, that is > using perf (or a perf equivalent), to hook onto that tracepoint. I probably wasn't as clear as I should have been. I think it would be helpful if you demonstrated how one would take the SELinux data in the perf event and translated that into something meaningful. --=20 paul moore www.paul-moore.com