Date: Tue, 4 Sep 2018 14:05:43 -0700 From: Conrad Meyer <cem@freebsd.org> To: Lev Serebryakov <lev@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, freebsd-fs <freebsd-fs@freebsd.org>, Xin LI <delphij@freebsd.org> Subject: Re: newfs silently fails if random is not ready (?) Message-ID: <CAG6CVpWmXPUZAozTdJa%2BrczVyo9wHqr=uLP2U-O%2BPytSWr6_Ug@mail.gmail.com> In-Reply-To: <1942661439.20180904235514@serebryakov.spb.ru> References: <609400979.20180904230820@serebryakov.spb.ru> <CAG6CVpWzaBGvEdpNBrMQSPkxBn6pybP0SWyuYUhg0Qev4RvLwA@mail.gmail.com> <1942661439.20180904235514@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Lev, On Tue, Sep 4, 2018 at 1:55 PM, Lev Serebryakov <lev@freebsd.org> wrote: > Tuesday, September 4, 2018, 11:37:59 PM, you wrote: >> Is newfs tripping on a raise()/abort() in arc4random(3) / >> getentropy(3)? > Nope, it is silently does nothing I think it is tripping on raise/abort() in one of these routines, but nothing is printing that information. See below. >> Is your program that runs newfs checking for non-zero >> exit status? > It is not "my" program, it is system mdmfs(8), and it checks exit > statuses, as far as I can see from source code. Ah, thanks. I missed this. mdmfs(8) has a bug in its run() function. It treats programs that exit with a signal (KILL, ABRT, ILL, SEGV...) the same as programs that exit with success. This is a (major) problem and the reason raise/abort is not visible. Best, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpWmXPUZAozTdJa%2BrczVyo9wHqr=uLP2U-O%2BPytSWr6_Ug>