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.1 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 82F87C2D0F1 for ; Mon, 30 Mar 2020 20:45:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5B92120757 for ; Mon, 30 Mar 2020 20:45:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="sNCyQM7d" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728123AbgC3Ups (ORCPT ); Mon, 30 Mar 2020 16:45:48 -0400 Received: from mail-qt1-f193.google.com ([209.85.160.193]:36455 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727328AbgC3Upr (ORCPT ); Mon, 30 Mar 2020 16:45:47 -0400 Received: by mail-qt1-f193.google.com with SMTP id m33so16437327qtb.3; Mon, 30 Mar 2020 13:45:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=FFzlxLM1vgVJfHIOAtCmkgRX5Ovtm5xzqT5SoJ3HlAU=; b=sNCyQM7dq5e5mkE22UbeVpP0svxqdXkfdWCtKGSczYBUKFEf0Y2bQrbN02n1BuFEX8 fUbGOA8f09O5WiKJtUx3Go4svlrlY8d/i8BKvDoUjEl2tEkxNJ0qzcdMe9BGaS2bNJ7E u7xFWgVdAndjgi3fGDJg5QGJQQOQVX716szt929ZvVBJ3DYQlxDTAkYIj/bTH4aIffKf 0o19URmrIO8AHzcQIVk5/J1MdVD/Mkrtz1O8CUcIM0+oInrtn88AA8e1KcZuUWTzuqrk d8lS/ib6IoCIA+j65xm9sF8O0wX8qSjsNAihz0F0qw0b5qOAhB/R2bIl7KHaza1HHqcY /qzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FFzlxLM1vgVJfHIOAtCmkgRX5Ovtm5xzqT5SoJ3HlAU=; b=afB+8v53VVqqOp3MwAVEiaSe9aBQb+LGvBY/WwOKy45i3Ncwsx5YscwYcqaCxbx3IK uAP/TAh/28D/v9hteqXsJSWNVA8u9X3nOGiqGQzban/jd3jrjG8rU4SiS9wigNNqjPRh JT0aCNSkOZU7MjkDsu6UHZQDmqo0Jw1kfMSd4FEPGEpGaWh4pXy5yyK43Vaw96vbh/A0 HolonIwo1xQhr65kI2ZDefNlwdqqlUelH2I1OpMAW7ZOLDtWPyQ6oCZGrdx4CbWNwkoM XTkNJv28u8O1JvF4w1DwDF17l1kmqJV3DNYA/nvERn9XAXhvfd8GRA5kaA9DNkZ4xCkO eWbQ== X-Gm-Message-State: ANhLgQ0V0bi/8X/KOAHjYunxayBGqNsyreXI50gloZPyp8290gieWa7V eC7vSxCM4NapMae/S09xyhk= X-Google-Smtp-Source: ADFU+vsb9ztTQllrb6dkhXGA01Im6N8C2YiemiN6F4YGtB3Wv0IFQxE/AXfdzeCasQbYwAdE9lm8Jg== X-Received: by 2002:ac8:60a:: with SMTP id d10mr2008212qth.140.1585601146077; Mon, 30 Mar 2020 13:45:46 -0700 (PDT) Received: from ?IPv6:2601:282:803:7700:6833:d88e:92a1:cac9? ([2601:282:803:7700:6833:d88e:92a1:cac9]) by smtp.googlemail.com with ESMTPSA id l22sm11737843qkj.120.2020.03.30.13.45.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 30 Mar 2020 13:45:45 -0700 (PDT) Subject: Re: [PATCH v3 bpf-next 0/4] Add support for cgroup bpf_link To: Andrii Nakryiko Cc: Andrii Nakryiko , bpf , Networking , Alexei Starovoitov , Daniel Borkmann , Andrey Ignatov , Kernel Team References: <20200330030001.2312810-1-andriin@fb.com> From: David Ahern Message-ID: <662788f9-0a53-72d4-2675-daec893b5b81@gmail.com> Date: Mon, 30 Mar 2020 14:45:44 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On 3/30/20 2:20 PM, Andrii Nakryiko wrote: >> The observability piece should go in the same release as the feature. > You mean LINK_QUERY command I mentioned before? Yes, I'm working on > adding it next, regardless if this patch set goes in right now or > later. There was also mention of a "human override" details of which have not been discussed. Since the query is not ready either, then the create/update should wait so that all of it can be in the same kernel release. As it stands it is a half-baked feature.