Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3498667ybc; Mon, 25 Nov 2019 15:47:21 -0800 (PST) X-Google-Smtp-Source: APXvYqzQKJN0F8kiaFm2F2UAFsICjay3luvxP+BtbGVZqTFJKmcWxUfRaQGOHO+MY1GAELIaEDN9 X-Received: by 2002:a05:6402:1718:: with SMTP id y24mr21219693edu.220.1574725641502; Mon, 25 Nov 2019 15:47:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574725641; cv=none; d=google.com; s=arc-20160816; b=YawtFZVcUdU9umXtj8olqoI7qmxlDnY7TTtokB2ay0GdIBhX2lKkY1PDYO6vZivkRk fSiiUUeum+mY5aFRI84IicsvFo0REGPX/2P1HfB4+o6nHR0YQ4mNo1oOy1wv0qn1yqTG DYkRS2+zrjCM1N1VzkfEghQGPTea9KFo1QAM2sAoHvd2OVRTHiUks8twP1lugCIg88t9 whWHF4KwoWNxJHISk/JIdY61GEUCc/BYuL5STefJJojC4unuR38gFhM+NPa5q6Z2SC6o lsARVJ6dBxG9T1kq8x1QGJRN74vDpghujLZI+5FeFYYqCmGgkPwkotgtg69C2h414DMj on3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=WMDeAcbZMWSPJMBANRYNfknq2XJvnNPf3T3fbDniwfE=; b=srM2WMZAe8WOLNtVz2boiZXhn89NYV2fBkN0R5iI5Y7hnqqMpk/oAdK8BQjdIiC1au Bf+9OP9I8xw8QtjGBorRoo3wv0TTsPBYkxXg7Sy1sPhkgIp1xhjjRm9AfEMJAWFJepio 4RBzLErMf7YKFW8Nu1+0vNpwfm4cVpAM3f9SDIG/9CUolG2Nzoyek1s2DbGz6zxLOdlH aDT/PqN3noeGk/w+zOl4kB5C/+hwVpo8I+Xqd/zBAk3mCZiCqLRGOh2xOiUJujkAQAgg 2ZTavd41tSb3NYmC6giK6liv9k96teuGkfHLTB1xJBbnnOERFwWq5hCAwJrVuceq2doO 7+wg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=f8JuR9ii; 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=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w26si5656403eju.48.2019.11.25.15.46.57; Mon, 25 Nov 2019 15:47:21 -0800 (PST) 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=@nvidia.com header.s=n1 header.b=f8JuR9ii; 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=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727156AbfKYXpT (ORCPT + 99 others); Mon, 25 Nov 2019 18:45:19 -0500 Received: from hqemgate14.nvidia.com ([216.228.121.143]:3045 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725940AbfKYXpS (ORCPT ); Mon, 25 Nov 2019 18:45:18 -0500 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate14.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 25 Nov 2019 15:45:21 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Mon, 25 Nov 2019 15:45:18 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Mon, 25 Nov 2019 15:45:18 -0800 Received: from [10.110.48.28] (10.124.1.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Nov 2019 23:45:17 +0000 Subject: Re: [PATCH] bpf: fix a no-mmu build failure by providing a stub allocator To: Daniel Borkmann , Andrii Nakryiko CC: Song Liu , John Fastabend , Johannes Weiner , Linux Next Mailing List , , , , LKML , kbuild test robot References: <20191125234103.1699950-1-jhubbard@nvidia.com> <20191125234103.1699950-2-jhubbard@nvidia.com> <8c4d892a-73b5-b4d5-be15-bc81e8297de9@iogearbox.net> X-Nvconfidentiality: public From: John Hubbard Message-ID: <735f27ed-65dd-d132-e6b4-20ba5749876c@nvidia.com> Date: Mon, 25 Nov 2019 15:45:17 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <8c4d892a-73b5-b4d5-be15-bc81e8297de9@iogearbox.net> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To HQMAIL107.nvidia.com (172.20.187.13) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1574725521; bh=WMDeAcbZMWSPJMBANRYNfknq2XJvnNPf3T3fbDniwfE=; h=X-PGP-Universal:Subject:To:CC:References:X-Nvconfidentiality:From: Message-ID:Date:User-Agent:MIME-Version:In-Reply-To: X-Originating-IP:X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=f8JuR9ii0ljL+Rl9x2Epbdw3yXw2DiLEhV4ImlGOXOb2aEMhIxpnhMyxcOodL7KKS 3sCS/OSXJ5rBN910/7NLXae6d1kMXDHY5I8Kp9T/grvpttQkqodE1Gyf+ocjE0qbm/ pt8XKSvPtWYzQYmRMdGFjJUZ7I8S8qcMXcq0UmLVrSuhdPGoDnXt4HIkned6uY3L5k m9LPTdpvBxb5/wUWAmik2+rrxlN1Nnohx+fIREjzS3SOYZkLw3J8qLVSLmrswxvmDU PBFALk1N8P/TjfFzmIP09qtwosruAeG9YZTGaW4P455xmvL07vLGmhaDZ5PMqTLN6c 8MyrithA3laFg== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/25/19 3:43 PM, Daniel Borkmann wrote: > On 11/26/19 12:41 AM, John Hubbard wrote: >> Commit fc9702273e2e ("bpf: Add mmap() support for BPF_MAP_TYPE_ARRAY") >> added code that calls vmalloc_user_node_flags() and therefore requires >> mm/vmalloc.c. However, that file is not built for the !CONFIG_MMU case. >> This leads to a build failure when using ARM with the config provided >> by at least one particular kbuild test robot report [1]. >> >> [1] https://lore/kernel.org/r/201911251639.UWS3hE3Y%lkp@intel.com >> >> Fix the build by providing a stub function for __bpf_map_area_alloc(). >> >> Fixes: fc9702273e2e ("bpf: Add mmap() support for BPF_MAP_TYPE_ARRAY") >> Reported-by: kbuild test robot >> Cc: Andrii Nakryiko >> Cc: Daniel Borkmann >> Cc: Song Liu >> Cc: John Fastabend >> Cc: Johannes Weiner >> Signed-off-by: John Hubbard > > Thanks for the patch, already fixed via: > > https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=ed81745a4c96841937f1da35c0eb66ac312e1480 OK, good, that's a better fix, too. Appreciate the quick answers! thanks, -- John Hubbard NVIDIA