Date: Mon, 5 Aug 2019 20:10:43 +0200 (CEST) From: =?UTF-8?Q?Trond_Endrest=C3=B8l?= <trond.endrestol@ximalas.info> To: freebsd-current@freebsd.org Cc: kib@freebsd.org Subject: Re: r350484 and ASLR enabled - init died (signal 6, exit 0) Message-ID: <alpine.BSF.2.21.99999.352.1908051947580.31116@enterprise.ximalas.info> In-Reply-To: <20190805130255.GA1121@albert.catwhisker.org> References: <alpine.BSF.2.21.99999.352.1908051436050.31116@enterprise.ximalas.info> <20190805130255.GA1121@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Aug 2019 06:02-0700, David Wolfskill wrote:
> On Mon, Aug 05, 2019 at 02:53:04PM +0200, Trond Endrestøl wrote:
> > Hi,
> >
> > Has anyone else noticed the kernel being unable to spawn init lately?
> >
> > All I get is:
> >
> > init died (signal 6, exit 0)
> > panic: Going nowhere without my init!
> >
> > /sbin/init hasn't had any changes in 4 months, and is present in /sbin
> > in the new BE.
> >
> > I've tried and failed in VBox at home this weekend, and in Citrix
> > Hypervisor 8 at $WORK today. I think we can rule out the hypervisors.
> >
> > Last known working revision is r350400.
> >
> > There are numerous kernel changes between r350400 and r350583. I'll
> > try each revision in succession and see if I can identify any
> > culprits.
> > ...
>
> I have not seen the behavior in question; my last update was from
> r350566 to r350584 (and was quite uneventful).
>
> In each case, a "real machine" was used (laptop & a build machine).
After more trial and error, r350484 is the culprit for Citrix
Hypervisor 8.
I have these lines in /boot/loader.conf:
kern.elf32.aslr.enable="1"
kern.elf32.aslr.pie_enable="1"
kern.elf64.aslr.enable="1"
kern.elf64.aslr.pie_enable="1"
r350483 works like a charm, and so does r350484 iff I disable ASLR.
Reenabling ASLR and setting kern.elf{64,32}.aslr.stack_gap to zero has
no effect.
I've cc'd kib@ on this one.
I'm going home and see if VBox 6.0.10 exhibits the same behaviour.
--
Trond.
From owner-freebsd-current@freebsd.org Mon Aug 5 19:23:17 2019
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7FA6AAB301
for <freebsd-current@mailman.nyi.freebsd.org>;
Mon, 5 Aug 2019 19:23:17 +0000 (UTC)
(envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
server-signature RSA-PSS (4096 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 462SNN47XKz46T3
for <freebsd-current@freebsd.org>; Mon, 5 Aug 2019 19:23:16 +0000 (UTC)
(envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x75JN5ib022427
(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO);
Mon, 5 Aug 2019 22:23:08 +0300 (EEST)
(envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x75JN5ib022427
Received: (from kostik@localhost)
by tom.home (8.15.2/8.15.2/Submit) id x75JN5jS022426;
Mon, 5 Aug 2019 22:23:05 +0300 (EEST)
(envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
using -f
Date: Mon, 5 Aug 2019 22:23:05 +0300
From: Konstantin Belousov <kostikbel@gmail.com>
To: Trond =?utf-8?Q?Endrest=C3=B8l?= <trond.endrestol@ximalas.info>
Cc: freebsd-current@freebsd.org
Subject: Re: r350484 and ASLR enabled - init died (signal 6, exit 0)
Message-ID: <20190805192305.GC2731@kib.kiev.ua>
References: <alpine.BSF.2.21.99999.352.1908051436050.31116@enterprise.ximalas.info>
<20190805130255.GA1121@albert.catwhisker.org>
<alpine.BSF.2.21.99999.352.1908051947580.31116@enterprise.ximalas.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <alpine.BSF.2.21.99999.352.1908051947580.31116@enterprise.ximalas.info>
User-Agent: Mutt/1.12.1 (2019-06-15)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM,
NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home
X-Rspamd-Queue-Id: 462SNN47XKz46T3
X-Spamd-Bar: -
Authentication-Results: mx1.freebsd.org; dkim=none;
dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com
(policy=none);
spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor
denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com
X-Spamd-Result: default: False [-1.98 / 15.00]; ARC_NA(0.00)[];
NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; RCVD_TLS_ALL(0.00)[];
FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[];
FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain];
HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all];
IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[];
NEURAL_HAM_SHORT(-0.99)[-0.988,0]; RCPT_COUNT_TWO(0.00)[2];
IP_SCORE(0.00)[ip: (-2.49), ipnet: 2001:470::/32(-4.51), asn: 6939(-2.90),
country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[];
R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+];
ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US];
RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com];
DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2019 19:23:17 -0000
On Mon, Aug 05, 2019 at 08:10:43PM +0200, Trond Endrestøl wrote:
> On Mon, 5 Aug 2019 06:02-0700, David Wolfskill wrote:
>
> > On Mon, Aug 05, 2019 at 02:53:04PM +0200, Trond Endrestøl wrote:
> > > Hi,
> > >
> > > Has anyone else noticed the kernel being unable to spawn init lately?
> > >
> > > All I get is:
> > >
> > > init died (signal 6, exit 0)
> > > panic: Going nowhere without my init!
> > >
> > > /sbin/init hasn't had any changes in 4 months, and is present in /sbin
> > > in the new BE.
> > >
> > > I've tried and failed in VBox at home this weekend, and in Citrix
> > > Hypervisor 8 at $WORK today. I think we can rule out the hypervisors.
> > >
> > > Last known working revision is r350400.
> > >
> > > There are numerous kernel changes between r350400 and r350583. I'll
> > > try each revision in succession and see if I can identify any
> > > culprits.
> > > ...
> >
> > I have not seen the behavior in question; my last update was from
> > r350566 to r350584 (and was quite uneventful).
> >
> > In each case, a "real machine" was used (laptop & a build machine).
>
> After more trial and error, r350484 is the culprit for Citrix
> Hypervisor 8.
>
> I have these lines in /boot/loader.conf:
>
> kern.elf32.aslr.enable="1"
> kern.elf32.aslr.pie_enable="1"
>
> kern.elf64.aslr.enable="1"
> kern.elf64.aslr.pie_enable="1"
>
> r350483 works like a charm, and so does r350484 iff I disable ASLR.
>
> Reenabling ASLR and setting kern.elf{64,32}.aslr.stack_gap to zero has
> no effect.
>
> I've cc'd kib@ on this one.
>
> I'm going home and see if VBox 6.0.10 exhibits the same behaviour.
Try r350608. There was a mis-merge in the committed patch (more serious
part), and some limits were not applied, which I did not see in my
testing due to the mismatch between stock FreeBSD and my testing
environment.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.99999.352.1908051947580.31116>