Received: by 10.213.65.68 with SMTP id h4csp849598imn; Tue, 20 Mar 2018 17:40:26 -0700 (PDT) X-Google-Smtp-Source: AG47ELsNn+w/Imgmn90ZvyOnu2H3IQzLLpPnx/a3QdXc4B5k6tky3kvhq201vSs8ij9AKlormvM+ X-Received: by 10.99.120.196 with SMTP id t187mr13744114pgc.149.1521592826164; Tue, 20 Mar 2018 17:40:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521592826; cv=none; d=google.com; s=arc-20160816; b=mqRp/RGCJo99gY9FPftyw3UB7WroHmlTIwFlwog6labBcFucqpV2Mebu7MC09YbkJ/ AC4YPBqt2b3v2NR7+f7m+gimamTGzzu98xdS5zR5JiB6tgbOH2VsbcvD9vUMOH1Ot4mm owQB+GYPbYNr2x8kJtEk2a2OpD7yS4fDrbd4uyEpnF7JtYz9zIg/ycgtg/9eOZ3rmiaI pSRZNU4V/Impk2RY2/AfoFtRUts8wpl/DtCI1tfPYa5F/9l698ixwih3PXZ7Fw8ZyjMa Pg8XrrITqHjsKtaEc1PKhBTqND3NdduRbaj2guoZjJFF2NuMZW0UpLDb5Q4fAOu+8ykX rRHg== 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:arc-authentication-results; bh=0Q8RF2HaWy3NLdlBXHQDa+96fzfVvSJfF6FjML2Q7LI=; b=w6T4EZ4UE3O7wAKZjcf0OemYl3eeERwIrY+B9q34TdHSnljmYvlbkE4hTumAFCAkDl RnE4dfBtq+AtJG026aq2YUNKOIr+2FqYhuZemQKZ5OSbYVHrjbifa83SI4P/lXHUimRA qxH4XFRK+22YVIF2kgdH6ebsojBOqohAXgilDQ2jAbfnF202MRY0D9KGF1mGTpsjzaJH 1tFoNO8w+EOnobtOM2npwzaqzjYYne6KNnTpUESIXXkDl9Shy4YioN2SkUMjMA8/RSZB DJH39nB+x/Bmj9unAVXjSsGwcrDnNdtbrJrG6jS29Ak3enCepBSdFFPExle3mx/jLC0R Fzmg== 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 f59-v6si2684919plb.38.2018.03.20.17.40.11; Tue, 20 Mar 2018 17:40:26 -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; 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 S1751805AbeCUAiu (ORCPT + 99 others); Tue, 20 Mar 2018 20:38:50 -0400 Received: from www62.your-server.de ([213.133.104.62]:40061 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751747AbeCUAit (ORCPT ); Tue, 20 Mar 2018 20:38:49 -0400 Received: from [62.202.221.10] (helo=linux.home) by www62.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-SHA:256) (Exim 4.85_2) (envelope-from ) id 1eyRm9-0006AA-Lx; Wed, 21 Mar 2018 01:38:45 +0100 Subject: Re: [PATCH] kbuild: disable clang's default use of -fmerge-all-constants To: Linus Torvalds Cc: Alexei Starovoitov , psodagud@codeaurora.org, Network Development , Chenbo Feng , Richard Smith , Chandler Carruth , Linux Kernel Mailing List References: <20180321001824.8395-1-daniel@iogearbox.net> From: Daniel Borkmann Message-ID: Date: Wed, 21 Mar 2018 01:38:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Authenticated-Sender: daniel@iogearbox.net X-Virus-Scanned: Clear (ClamAV 0.99.3/24405/Wed Mar 21 00:08:08 2018) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/21/2018 01:36 AM, Linus Torvalds wrote: > On Tue, Mar 20, 2018 at 5:18 PM, Daniel Borkmann wrote: >> Prasad reported that he has seen crashes in BPF subsystem with netd >> on Android with arm64 in the form of (note, the taint is unrelated): > > Ack. This looks good to me. And thanks for noticing the behavior wrt > the correct gcc merging. > >> [ Hi Linus, feel free to take this fix directly if you want. >> Alternatively, we could route it via bpf tree. Thanks a >> lot for your feedback! ] > > So since it's your patch and the only known issue comes from the bpf > side, I think it should just go through the bpf tree, and I expect it > to get to me through all the usual channels. Yeah, that's fine, thanks for letting us know! Best, Daniel