newfs silently fails if random is not ready (?)

Conrad Meyer cem at
Tue Sep 4 21:05:46 UTC 2018

Hi Lev,

On Tue, Sep 4, 2018 at 1:55 PM, Lev Serebryakov <lev at> 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.


More information about the freebsd-fs mailing list