On Fri, Sep 19, 2014 at 11:23:54AM +0200, Natanael Copa wrote:
> On Thu, 18 Sep 2014 09:04:15 -0700
> Isaac Dunham <ibid.ag_at_gmail.com> wrote:
>
> > On Thu, Sep 18, 2014 at 04:53:27PM +0200, Natanael Copa wrote:
> > >
> > > I wonder what is going on. Maybe the CONFIG_RELOCATABLE change
> > > mentioned above is related? I have no idea...
> >
> > I'm suspecting that might be it.
> >
> > It's not a bug in the build environment, since the exact same system
> > could build a working 3.14.17 and a non-working 3.14.18.
> > That's what the test matrix was about.
>
> It is CONFIG_RANDOMIZE_BASE=y that triggers it.
>
> I have disabled that again on x86 vanilla kernel (and will do so on
> grsec kernel too which also seems to be affected)
>
> Thanks you for reporting it, for your help finding the cause and for
> your patience.
Does this occur with kmod (ie, is Busybox being overly simplistic,
or does this flat-out break the kernel?)
I suppose that it should be reported to either kernel.org or Busybox,
depending which it is.
Thanks,
Isaac Dunham
---
Unsubscribe: alpine-devel+unsubscribe_at_lists.alpinelinux.org
Help: alpine-devel+help_at_lists.alpinelinux.org
---
Received on Fri Sep 19 2014 - 07:11:24 UTC