From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752273AbcDSCdo (ORCPT ); Mon, 18 Apr 2016 22:33:44 -0400 Received: from mga01.intel.com ([192.55.52.88]:50363 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751921AbcDSCdm (ORCPT ); Mon, 18 Apr 2016 22:33:42 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,504,1455004800"; d="scan'208";a="688491403" Date: Tue, 19 Apr 2016 10:33:34 +0800 From: Fengguang Wu To: Alexei Starovoitov Cc: Arnd Bergmann , "David S . Miller" , netdev@vger.kernel.org, Steven Rostedt , Ingo Molnar , Alexei Starovoitov , Daniel Borkmann , linux-kernel@vger.kernel.org, Philip Li Subject: Re: [PATCH] bpf: avoid warning for wrong pointer cast Message-ID: <20160419023334.GC24067@wfg-t540p.sh.intel.com> References: <1460838585-1248139-1-git-send-email-arnd@arndb.de> <20160417004740.GA80675@ast-mbp.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160417004740.GA80675@ast-mbp.thefacebook.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Alexei, On Sat, Apr 16, 2016 at 05:47:42PM -0700, Alexei Starovoitov wrote: > On Sat, Apr 16, 2016 at 10:29:33PM +0200, Arnd Bergmann wrote: > > Two new functions in bpf contain a cast from a 'u64' to a > > pointer. This works on 64-bit architectures but causes a warning > > on all 32-bit architectures: > > > > kernel/trace/bpf_trace.c: In function 'bpf_perf_event_output_tp': > > kernel/trace/bpf_trace.c:350:13: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast] > > u64 ctx = *(long *)r1; > > > > This changes the cast to first convert the u64 argument into a uintptr_t, > > which is guaranteed to be the same size as a pointer. > > > > Signed-off-by: Arnd Bergmann > > Fixes: 9940d67c93b5 ("bpf: support bpf_get_stackid() and bpf_perf_event_output() in tracepoint programs") > > Thanks. > Acked-by: Alexei Starovoitov > > I guess I started to rely on 0-day build-bot too much. > This patch has been in my tree for 2+ weeks and then in net-next and > I didn't receive a single email from build-bot about this warning, > though I do receive them for my other work-in-progress stuff. Odd. > Fengguang, any idea why build-bot sometimes silent? Sorry I went off for some time.. Philip, would you help have a check? Thanks, Fengguang