Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2698688ybb; Mon, 30 Mar 2020 11:08:37 -0700 (PDT) X-Google-Smtp-Source: ADFU+vtxaIDC6t6XdUgU+Ktxx0Jc4OJPXkGVBAPrF1bFXvyVg8TJZYwn6EovtJIwoU1Yg7fIw/Fx X-Received: by 2002:a54:4181:: with SMTP id 1mr439790oiy.158.1585591717534; Mon, 30 Mar 2020 11:08:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585591717; cv=none; d=google.com; s=arc-20160816; b=NEb3XWN/BBUEqIPTcw1Cq7PHOyTsyJgBFNpz3ofeUDJ7PKk4NDsGnbtWTREoqSdy0R 6TqYa4nEBEak23FNXZZwXSC6EOFtiEE1ZMiyLN5myZQUO1tIRvEq+3W22Tj71q9zTLck h5d+IwW5hQ343/2f369kYtD6W7ktWLYMl0niCWcnDuZNPrEdxfPdU+x8+4S6CGd1ncdR oRDKtGH+4CiM3U+TjFNd57Htn/nEvbDZif0bfHwjvD/BBF23IzZztakRcWCxN/S/jWpg K3kjQT5yEik41q9vsntkItpPhLyZAuWl+u/nas/1CzNI/WZ1icQzJvJBgsDfLCL9kOsX 5Tiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:date:from:dkim-signature; bh=eK8x7gAXMov1inBTyCa9T4MtcTyNUJQUaxWPoEq8WPM=; b=Mqxc5UwNv2mtMj2As5poVq/F9ZK8mWv+LY4F6LBk6uBhaoivZTSkzQKe0dhKBHYAy4 KS5lN+W1q8zrOowBrPzPRDG3+1/tqUuI0lOz7b0i6OFzGq9qHXEU1TmWiuLnDNIoOdwg OM44cXXzhjcWImWodr6zx0YmPiD4SazjOAT6Dbw9KBe/vAqGQrYrVVKzyDjv1JhbOmqX J0nnxXN1CjtwO/5cwHrVcwaNjgPU+7OlLDyAJdoZ2H8mo3bGpmYrzSXaBKnF0FCFKS46 en7naW/TTnR7mpjcsWTT6gPMezxXNO/qEHGnEBU5Iz4VGl7aHG68TtQf1MH7Vw1HFDhp zmrw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=WQE+QWOm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q12si6394124ooi.0.2020.03.30.11.08.21; Mon, 30 Mar 2020 11:08:37 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=WQE+QWOm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728043AbgC3SFn (ORCPT + 99 others); Mon, 30 Mar 2020 14:05:43 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:39463 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727975AbgC3SFn (ORCPT ); Mon, 30 Mar 2020 14:05:43 -0400 Received: by mail-wr1-f68.google.com with SMTP id p10so22840914wrt.6 for ; Mon, 30 Mar 2020 11:05:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=eK8x7gAXMov1inBTyCa9T4MtcTyNUJQUaxWPoEq8WPM=; b=WQE+QWOmy+rAqfpi/9XWYmLS7jKwH6IbEwVcxVE/K6tVdNy/4xbN85nlusDSzm757a N8Esq9fl5Qh8a89xDGWWUQzzWddG3vupEw//z1mNposwwR3yEPcMIPJRq7YVVtoKQP+p SKQfYVxP6q6j+vCw/suwHBGl91DNojYqK1BMQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=eK8x7gAXMov1inBTyCa9T4MtcTyNUJQUaxWPoEq8WPM=; b=TAiR+4rfROuFDFSH//HmJqarYSbbYy1eCMr9FTupFpeVxAycgC2qQdqPVp/hk4Etga 8G9/az7TOrDvt5KqGOAA+vg5Z1pBoKH5UxQZzMpS/Dm8KBbUXQQCr8y8qONPQZKEOE2j tmf8WhrRbYYUzzI2FU+9WwqAGSarsaoEfRFC83snMV964BXmTqyXnAkc7Rvx1e78DJ1t 2GhHylm1QjqCZHZNTpSTSrhA/KkZ9EmiB5DGcas1Orea4YkuQBmDnWyeKP3K0XxlzHMq dt1ST3ZPVKfPxzT23Z60FAAkxPQV3nyvTZfiCexBPv2OwR6hzzZHNQpuW6jN4JOakcCS qOTA== X-Gm-Message-State: ANhLgQ0yWFKCeOjzjqqkj89CJwWdN5NLNolTNxhcsIjewKh3J4Yer3W/ YWpMgteYu+WPMY1iaKaIBtANmA== X-Received: by 2002:adf:e946:: with SMTP id m6mr16493103wrn.187.1585591540289; Mon, 30 Mar 2020 11:05:40 -0700 (PDT) Received: from google.com ([2a00:79e0:42:204:8a21:ba0c:bb42:75ec]) by smtp.gmail.com with ESMTPSA id l4sm21826103wru.1.2020.03.30.11.05.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 30 Mar 2020 11:05:39 -0700 (PDT) From: KP Singh X-Google-Original-From: KP Singh Date: Mon, 30 Mar 2020 20:05:38 +0200 To: KP Singh Cc: Daniel Borkmann , Randy Dunlap , Stephen Rothwell , Linux Next Mailing List , Linux Kernel Mailing List , bpf , "netdev@vger.kernel.org" Subject: Re: linux-next: Tree for Mar 30 (bpf) Message-ID: <20200330180538.GA180081@google.com> References: <20200330204307.669bbb4d@canb.auug.org.au> <86f7031a-57c6-5d50-2788-ae0e06a7c138@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30-Mar 19:54, KP Singh wrote: So, it looks like bpf_tracing_func_proto is only defined when CONFIG_BPF_EVENTS is set: obj-$(CONFIG_BPF_EVENTS) += bpf_trace.o We have a few options: * Add a __weak symbol for bpf_tracing_func_proto which we have done in the past for similar issues. This however, does not make much sense, as CONFIG_BPF_LSM cannot really do much without its helpers. * Make CONFIG_BPF_LSM depend on CONFIG_BPF_EVENTS, this should solve it, but not for this particular Kconfig that was generated. Randy, I am assuming if we add the dependency, this particular Kconfig won't be generated. I am assuming this patch now needs to be sent for "bpf" and not "bpf-next" as the merge window has opened? - KP > Thanks for adding me Daniel, taking a look. > > - KP > > On Mon, Mar 30, 2020 at 7:25 PM Daniel Borkmann wrote: > > > > [Cc KP, ptal] > > > > On 3/30/20 7:15 PM, Randy Dunlap wrote: > > > On 3/30/20 2:43 AM, Stephen Rothwell wrote: > > >> Hi all, > > >> > > >> The merge window has opened, so please do not add any material for the > > >> next release into your linux-next included trees/branches until after > > >> the merge window closes. > > >> > > >> Changes since 20200327: > > > > > > (note: linux-next is based on linux 5.6-rc7) > > > > > > > > > on i386: > > > > > > ld: kernel/bpf/bpf_lsm.o:(.rodata+0x0): undefined reference to `bpf_tracing_func_proto' > > > > > > > > > Full randconfig file is attached. > > > > >