From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Stable Kernel <stable@kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [GIT PULL] Xen bugfixes
Date: Thu, 10 Sep 2009 19:26:29 +0200 [thread overview]
Message-ID: <20090910172629.GA10689@elte.hu> (raw)
In-Reply-To: <4AA93466.6020607@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> 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: <stable@kernel.org>
> > tags for automatic back-merging requests. The fixes narrowly
> > missed v2.6.31.
> >
>
> Will do.
Thanks,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Tejun Heo <tj@kernel.org>,
Stable Kernel <stable@kernel.org>
Subject: Re: [GIT PULL] Xen bugfixes
Date: Thu, 10 Sep 2009 19:26:29 +0200 [thread overview]
Message-ID: <20090910172629.GA10689@elte.hu> (raw)
In-Reply-To: <4AA93466.6020607@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> 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: <stable@kernel.org>
> > tags for automatic back-merging requests. The fixes narrowly
> > missed v2.6.31.
> >
>
> Will do.
Thanks,
Ingo
next prev parent reply other threads:[~2009-09-10 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 23:51 [GIT PULL] Xen bugfixes Jeremy Fitzhardinge
2009-09-09 23:51 ` Jeremy Fitzhardinge
2009-09-10 5:16 ` Ingo Molnar
2009-09-10 5:16 ` Ingo Molnar
2009-09-10 17:16 ` Jeremy Fitzhardinge
2009-09-10 17:16 ` Jeremy Fitzhardinge
2009-09-10 17:26 ` Ingo Molnar [this message]
2009-09-10 17:26 ` Ingo Molnar
2009-09-10 19:02 ` Jeremy Fitzhardinge
2009-09-10 19:02 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2009-12-03 23:46 Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090910172629.GA10689@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@kernel.org \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.