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=-2.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 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 94D43C3A5A6 for ; Wed, 28 Aug 2019 04:49:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6C5EF2173E for ; Wed, 28 Aug 2019 04:49:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="nm7UJeT8" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726147AbfH1EtI (ORCPT ); Wed, 28 Aug 2019 00:49:08 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:34636 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725865AbfH1EtI (ORCPT ); Wed, 28 Aug 2019 00:49:08 -0400 Received: by mail-pg1-f195.google.com with SMTP id n9so729078pgc.1; Tue, 27 Aug 2019 21:49:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=Wqg7s2VUiWnCXp5xHQk0TWcvmJznRH+GklDYl3ugIDI=; b=nm7UJeT8VU8VVcVNeCtyOXAcJCJMMtDOitRvkRUTUjYR2y0wLqfAcohps+3AX2vzEu 2Ss8vu8CtJlLsRaDk5hEdiHwQ2JdXSkblDRgTc0Syx0KjAJsynvr6QgqPvBTiDCmh7j5 OnxERo8Vt+LBNFgQrzRKHokekpEYBL5lA0nr4F0rSp8r+Gm/k4ZWyukryWWNzixQgZdF I+lfmWz5NQOimMpCk2reWHe+SaLmE2zisVXUKlJr3uJ94edlxQ1Ipbh9HYlcYjT2Kr6L tOUQ/wk+yE1x8eHzdE4mzeYEwIeENLEyefpxFKjipDmnp4fFRkiJW9GUHcdrVQjU9P6L Z9GQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=Wqg7s2VUiWnCXp5xHQk0TWcvmJznRH+GklDYl3ugIDI=; b=mZnw1/kbEyEpFrisDiX4Ew71usXxBoVwY4bjRze0UDbxjH/PuU+W+26DRNUwH87oi2 +SBaq2Swl0f40n71kjm8EoM7QDmO8CiH4hPqhyl0OBAheowPMvSBCTUTcLhl2g4qOfe2 dcf6LZDPYlT+9fcp3ouyIRI04zk0tqtytrRXbjXPudvPErb9sHK25+Axwo/PCmB8V1ds xOEoDbTn+lqlxiTJhZvqnim+oTZJ08dhuHfgSfM03iUIALvmAr0r5mNtEeTOCiGPN51H 98Lb/YL+LT2euM7utSxCd8Xf6TgeyP2AqEY9p8LulXJCm8s8dCxJUvXoCxSZ4KQ7Wgvw g88w== X-Gm-Message-State: APjAAAXL7r5Xg+r/XDOE7pMvF0/RwjAJk0uM5NJmbmETyLV0tyxxfco6 vA2TRONaFI5/NbFFnt1J2eg= X-Google-Smtp-Source: APXvYqwqTRMDD2PNZbsRspgzW5nn2Eh6VJ2YQhL/gbSvytSSyRLGjMMEPHEzLxNmt8FgDx+JlCv94g== X-Received: by 2002:a63:dc4f:: with SMTP id f15mr1803659pgj.227.1566967747577; Tue, 27 Aug 2019 21:49:07 -0700 (PDT) Received: from ast-mbp.dhcp.thefacebook.com ([2620:10d:c090:180::86a2]) by smtp.gmail.com with ESMTPSA id r3sm1155539pfr.101.2019.08.27.21.49.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Aug 2019 21:49:06 -0700 (PDT) Date: Tue, 27 Aug 2019 21:49:05 -0700 From: Alexei Starovoitov To: Andy Lutomirski Cc: Alexei Starovoitov , Kees Cook , LSM List , James Morris , Jann Horn , Peter Zijlstra , Masami Hiramatsu , Steven Rostedt , "David S. Miller" , Daniel Borkmann , Network Development , bpf , kernel-team , Linux API Subject: Re: [PATCH bpf-next] bpf, capabilities: introduce CAP_BPF Message-ID: <20190828044903.nv3hvinkkolnnxtv@ast-mbp.dhcp.thefacebook.com> References: <20190827205213.456318-1-ast@kernel.org> <20190828003447.htgzsxs5oevn3eys@ast-mbp.dhcp.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180223 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, Aug 27, 2019 at 07:00:40PM -0700, Andy Lutomirski wrote: > > Let me put this a bit differently. Part of the point is that > CAP_TRACING should allow a user or program to trace without being able > to corrupt the system. CAP_BPF as you’ve proposed it *can* likely > crash the system. Really? I'm still waiting for your example where bpf+kprobe crashes the system...