Date: Mon, 22 Sep 2014 11:39:00 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Isaac Dunham <ibid.ag@gmail.com>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Re: Cannot mount root filesystem with latest
 vanilla kernel
Message-ID: <20140922113900.095faeb8@ncopa-desktop.alpinelinux.org>
In-Reply-To: <20140919141123.GA2020@newbook>
References: <20140914210508.GA1775@newbook>
	<20140915113105.182f422b@ncopa-desktop.alpinelinux.org>
	<20140915193509.GA545@muslin>
	<20140916045715.GA1781@newbook>
	<20140916234219.GA1783@newbook>
	<20140917160613.45155c68@ncopa-desktop.alpinelinux.org>
	<20140917154445.GA1783@newbook>
	<20140918165327.709c57f5@ncopa-desktop.alpinelinux.org>
	<20140918160414.GA25585@newbook>
	<20140919112354.2893501e@ncopa-desktop.alpinelinux.org>
	<20140919141123.GA2020@newbook>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 19 Sep 2014 07:11:24 -0700
Isaac Dunham <ibid.ag@gmail.com> wrote:

> 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@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 didn't have time to test that out.

> I suppose that it should be reported to either kernel.org or Busybox,
> depending which it is.

I suspect it is a bug in kernel actually, but am not sure.

I don't have capacity to follow it up at the moment. sorry :-/

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---