From: Ingo Molnar Subject: Re: [GIT PULL] Xen bugfixes Date: Thu, 10 Sep 2009 19:26:29 +0200 Message-ID: <20090910172629.GA10689@elte.hu> References: <4AA83F99.5040401@goop.org> <20090910051648.GA1335@elte.hu> <4AA93466.6020607@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4AA93466.6020607@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Xen-devel , the arch/x86 maintainers , Linux Kernel Mailing List , Ingo Molnar , Tejun Heo , Stable Kernel List-Id: xen-devel@lists.xenproject.org * Jeremy Fitzhardinge wrote: > On 09/09/09 22:16, Ingo Molnar wrote: > >> +# Make sure __phys_addr has no stackprotector > >> +nostackp := $(call cc-option, -fno-stack-protector) > >> +CFLAGS_ioremap.o := $(nostackp) > >> + > >> > > Sure we could move __phys_addr into its own file and thus avoid > > turning off stackprotector for the rest of ioremap.c? > > > > I'm not very keen on having zillions of tiny files just to cope > with the lack of per-function stackprotector disable. I don't see > any code in ioremap.c that would really benefit from > stack-protector anyway; there are no local arrays. > > At least __phys_addr and friends aren't terribly closely related > to ioremap so it would at least make some sense. Agreed, i wouldnt do it just for the stackprotector benefit (it's really stupid that GCC does not allow per function exceptions) - but here __phys_addr() looked out of place a bit. > [...] Patch below. Looks like a nice cleanup. Mind sticking it into your next pull request? > >> +CFLAGS_mmu.o := $(nostackp) > >> > > A similar argument could be made here - what proportion of mmu.c is > > affected? > > More. It would be a fairly arbitrary chunk of code to split out > into a separate file. Ok - i'd not do it then. > > Also, once the commits have hit upstream feel free bounce them > > to stable@kernel.org - they dont have Cc: > > tags for automatic back-merging requests. The fixes narrowly > > missed v2.6.31. > > > > Will do. Thanks, Ingo