Received: by 10.223.185.116 with SMTP id b49csp795858wrg; Wed, 14 Feb 2018 07:08:18 -0800 (PST) X-Google-Smtp-Source: AH8x2240UAJ4R3BKnB59X0GrpVKAKcYFWsgO9iRWXOcJGmyfRUXns7eV8rpq1oVToRW0nY4o+r+C X-Received: by 10.98.93.9 with SMTP id r9mr5031317pfb.55.1518620898343; Wed, 14 Feb 2018 07:08:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518620898; cv=none; d=google.com; s=arc-20160816; b=RYZIsoEapGmC9FAeuFK9onsFi1gw922oJmjC0IctgQRhC38bAXpQl+B+psQpFQXUzO KMlt8S0/uj/PaVGjH2T+St2dEx9766h8Y63AyMhb4ZnVw4VyZpxyNwS7F7UGNAcHe/Jp zkZeN6q/xDcZWvXlCS2Fezccd0RWPwRB7fnEvd1yCmhHWeHXJ6H/HJ6Bcm4QfEH5V8mz 9HP8Mheg6RVWibgodTSlsNlc3ea8SM+iAueodxre0zy7OaYpnOzNCamWeEL01uaYrTZZ GfnDNmkK9dlWu7EKFdPBhOXmA9VEz2mt43ehP+FnFX/xgGvAgTeQv3/QB3jSpTo+hHqK AQXw== 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:from:date:arc-authentication-results; bh=D4EKe5MXUDI9weBeDyJuD/3hWPUoFe6JOdPLE5cTXf8=; b=Cy90Mqnf4XaBGWLKtrS98SsOs1u1QcRL+w17VO3mVkuNqwr/6eCMNJkNIbPzPwr2ck uv7q6KLJYZIQ7+XyRbMC+E1U9INlCzL5mNz0UQtImeSJm3LdniziySidRkCejQYxI3GN KouL+iZ3rAAX1lQESTCsxP+GpBH7+gf440DGoIjT6rSfAalITnOutr4eVFtAtdi0R4vY +GMPKwIVnj6XD4ciwmFOo2NDQtSYZGIGEk/JOYvCE1GEsnlBL5a7E9M82mG5rV5w8zyo LEYfuAZOVDq3ys/RIzwIfbxT5CGC3Tp4VXKEmrKQsp7jIiNdVgq6JlYY9ijEEAorXf2E u/Mw== 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 o74si3442280pfj.76.2018.02.14.07.07.39; Wed, 14 Feb 2018 07:08:18 -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 S1031096AbeBNPGp (ORCPT + 99 others); Wed, 14 Feb 2018 10:06:45 -0500 Received: from mx2.suse.de ([195.135.220.15]:37102 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031006AbeBNPGn (ORCPT ); Wed, 14 Feb 2018 10:06:43 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 9AB45AED9; Wed, 14 Feb 2018 15:06:41 +0000 (UTC) Date: Wed, 14 Feb 2018 16:06:40 +0100 From: Michal Hocko To: Jason Wang Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, mst@redhat.com, Matthew Wilcox , Jesper Dangaard Brouer , akpm@linux-foundation.org, dhowells@redhat.com, hannes@cmpxchg.org Subject: Re: [PATCH net] bpf: cpumap: use GFP_KERNEL instead of GFP_ATOMIC in __cpu_map_entry_alloc() Message-ID: <20180214150640.GC3443@dhcp22.suse.cz> References: <1518617854-4486-1-git-send-email-jasowang@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1518617854-4486-1-git-send-email-jasowang@redhat.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 14-02-18 22:17:34, Jason Wang wrote: > There're several implications after commit 0bf7800f1799 ("ptr_ring: > try vmalloc() when kmalloc() fails") with the using of vmalloc() since > can't allow GFP_ATOMIC but mandate GFP_KERNEL. This will lead a WARN > since cpumap try to call with GFP_ATOMIC. Fortunately, entry > allocation of cpumap can only be done through syscall path which means > GFP_ATOMIC is not necessary, so fixing this by replacing GFP_ATOMIC > with GFP_KERNEL. map_update_elem does the following. Unless I am missing something and the callback doesn't call cpu_map_update_elem there then we are in a non-preemptible context there and GFP_WAIT would blow up. rcu_read_lock(); err = map->ops->map_update_elem(map, key, value, attr->flags); rcu_read_unlock(); > Reported-by: syzbot+1a240cdb1f4cc88819df@syzkaller.appspotmail.com > Fixes: 0bf7800f1799 ("ptr_ring: try vmalloc() when kmalloc() fails") > Cc: Michal Hocko > Cc: Daniel Borkmann > Cc: Matthew Wilcox > Cc: Jesper Dangaard Brouer > Cc: akpm@linux-foundation.org > Cc: dhowells@redhat.com > Cc: hannes@cmpxchg.org > Signed-off-by: Jason Wang > --- > kernel/bpf/cpumap.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/kernel/bpf/cpumap.c b/kernel/bpf/cpumap.c > index fbfdada6..a4bb0b3 100644 > --- a/kernel/bpf/cpumap.c > +++ b/kernel/bpf/cpumap.c > @@ -334,7 +334,7 @@ static int cpu_map_kthread_run(void *data) > static struct bpf_cpu_map_entry *__cpu_map_entry_alloc(u32 qsize, u32 cpu, > int map_id) > { > - gfp_t gfp = GFP_ATOMIC|__GFP_NOWARN; > + gfp_t gfp = GFP_KERNEL | __GFP_NOWARN; > struct bpf_cpu_map_entry *rcpu; > int numa, err; > > -- > 2.7.4 -- Michal Hocko SUSE Labs