Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3497828ybc; Mon, 25 Nov 2019 15:46:14 -0800 (PST) X-Google-Smtp-Source: APXvYqz45CzZE6w1q+IflhkFsPObwjHht9eucryXPk2k8BPyGm+Mv2eR75Pr87q9qybaB6M/1mQh X-Received: by 2002:a17:906:7f8a:: with SMTP id f10mr41057879ejr.209.1574725573899; Mon, 25 Nov 2019 15:46:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574725573; cv=none; d=google.com; s=arc-20160816; b=G0rulCNp3msqFvqxwiuBBzW4p0h+ES+enh43shG2lpoawOkSWDa9d7tiSnPZr43CFC LbJyVyv0bPwQZIcDZvCZUiD9gTd1PgWDMJpRuWdUzlu4yXJ74B9QFE9Ribg9wcNXrhno xHv91rfIS8QC3A8PJWk1EzK6lCmvbz/W6bBwlIjLhYFgNuj9mXQk/GTYDvMD2iNKklTz 5una/1UpOb4Ve1pFAHOD5Ar6ncw1dulXNYHlSRrsfvC81ZEDwUfjvp88og+AtPe5TB3i flLweMaNgXhZnegnAxbxOEe+Zt3+d5puhwU2cJrHRMiJe2bp/4VQebP2jXSAMHMm9j65 e40g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=jPEX5gfE5XsR5XLxCoBbcHwnKXU6B5Z1Pu/5VCo0JNw=; b=OoiIyv7+afxbqbzG8iqdNcGedtSjQFDJTlGI7TyqNHhh4eic/5gI9J3bbkR76rIO9u FkJiP9v13ro4nMSnU7qPyGDaQJUAHpXhxpK7XGSjFiMCtTZiK2kqsVtn/Ign/eEF4hZ6 6LZXv6hG0jdv/kmXMK/nV94J+v0S2ZuU+fKvouuAN+m9vswS6BkZ+7/K7xG+uh14mOND m9DMup+d5caACj22v9b4r39GloLwdccFhuAcij0C2eoJFQbOupLpVAD4dCqc5UKGKnse LPnSH6FDDWsa1ktG97PV1Go15DJjDneNWVoT23MeiPhZHkccUTJoIZnOWItOZgXYSMnj oj9g== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s17si5608976ejr.267.2019.11.25.15.45.49; Mon, 25 Nov 2019 15:46:13 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727125AbfKYXnU (ORCPT + 99 others); Mon, 25 Nov 2019 18:43:20 -0500 Received: from www62.your-server.de ([213.133.104.62]:44712 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725912AbfKYXnT (ORCPT ); Mon, 25 Nov 2019 18:43:19 -0500 Received: from sslproxy06.your-server.de ([78.46.172.3]) by www62.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1iZO0e-0001rZ-CG; Tue, 26 Nov 2019 00:43:12 +0100 Received: from [178.197.248.11] (helo=pc-9.home) by sslproxy06.your-server.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1iZO0d-0007fK-T3; Tue, 26 Nov 2019 00:43:11 +0100 Subject: Re: [PATCH] bpf: fix a no-mmu build failure by providing a stub allocator To: John Hubbard , Andrii Nakryiko Cc: Song Liu , John Fastabend , Johannes Weiner , Linux Next Mailing List , bpf@vger.kernel.org, netdev@vger.kernel.org, linux-mm@kvack.org, LKML , kbuild test robot References: <20191125234103.1699950-1-jhubbard@nvidia.com> <20191125234103.1699950-2-jhubbard@nvidia.com> From: Daniel Borkmann Message-ID: <8c4d892a-73b5-b4d5-be15-bc81e8297de9@iogearbox.net> Date: Tue, 26 Nov 2019 00:43:10 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <20191125234103.1699950-2-jhubbard@nvidia.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Authenticated-Sender: daniel@iogearbox.net X-Virus-Scanned: Clear (ClamAV 0.101.4/25644/Mon Nov 25 10:54:22 2019) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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