From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincenzo Frascino Subject: Re: [PATCH v5 00/23] Unify vDSOs across more architectures Date: Thu, 28 Feb 2019 12:42:53 +0000 Message-ID: References: <20190222122430.21180-1-vincenzo.frascino@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Arnd Bergmann Cc: linux-arch , Shuah Khan , Rasmus Villemoes , Catalin Marinas , Daniel Lezcano , Will Deacon , Russell King , Ralf Baechle , Mark Salyzyn , Paul Burton , Dmitry Safonov <0x7f454c46@gmail.com>, Thomas Gleixner , Peter Collingbourne , Linux ARM List-Id: linux-arch.vger.kernel.org On 28/02/2019 12:38, Arnd Bergmann wrote: > On Thu, Feb 28, 2019 at 1:09 PM Vincenzo Frascino > wrote: >> >> thank you for testing my code. >> >> On 28/02/2019 11:40, Arnd Bergmann wrote: >>> On Fri, Feb 22, 2019 at 1:25 PM Vincenzo Frascino >>> wrote: >>> ^ >>> >>> I think this is all harmless, but we need to limit the set of header files >>> that can be included indirectly when compiling the vdso in arm32 mode. >>> >> >> I agree with you on the principle, but I am unable to replicate the warnings. >> Did you make any customization to the default defconfig? What is the top >> commit-id you have on your tree? > > I observed this on top of v5.0-rc7 earlier, and have since rebased to > today's linux-next, where it still happens with the regular 'make defconfig', > on all compiler versions I have (4.8 through 8.1). > Thanks, I will try to rebase my patches on linux-next and see if I can reproduce it. > Arnd > -- Regards, Vincenzo From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com ([217.140.101.70]:47098 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727914AbfB1Mm6 (ORCPT ); Thu, 28 Feb 2019 07:42:58 -0500 Subject: Re: [PATCH v5 00/23] Unify vDSOs across more architectures References: <20190222122430.21180-1-vincenzo.frascino@arm.com> From: Vincenzo Frascino Message-ID: Date: Thu, 28 Feb 2019 12:42:53 +0000 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: Arnd Bergmann Cc: linux-arch , Linux ARM , Catalin Marinas , Will Deacon , Russell King , Ralf Baechle , Paul Burton , Daniel Lezcano , Thomas Gleixner , Mark Salyzyn , Peter Collingbourne , Shuah Khan , Dmitry Safonov <0x7f454c46@gmail.com>, Rasmus Villemoes Message-ID: <20190228124253.8Cn0Tywv5uB0uKNisxyOQxFDCee1PpIRf7YENfCK1U8@z> On 28/02/2019 12:38, Arnd Bergmann wrote: > On Thu, Feb 28, 2019 at 1:09 PM Vincenzo Frascino > wrote: >> >> thank you for testing my code. >> >> On 28/02/2019 11:40, Arnd Bergmann wrote: >>> On Fri, Feb 22, 2019 at 1:25 PM Vincenzo Frascino >>> wrote: >>> ^ >>> >>> I think this is all harmless, but we need to limit the set of header files >>> that can be included indirectly when compiling the vdso in arm32 mode. >>> >> >> I agree with you on the principle, but I am unable to replicate the warnings. >> Did you make any customization to the default defconfig? What is the top >> commit-id you have on your tree? > > I observed this on top of v5.0-rc7 earlier, and have since rebased to > today's linux-next, where it still happens with the regular 'make defconfig', > on all compiler versions I have (4.8 through 8.1). > Thanks, I will try to rebase my patches on linux-next and see if I can reproduce it. > Arnd > -- Regards, Vincenzo