From owner-freebsd-current@freebsd.org Tue Sep 4 21:05:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF194FFBEF3; Tue, 4 Sep 2018 21:05:45 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CF0D8165B; Tue, 4 Sep 2018 21:05:45 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f50.google.com with SMTP id h1-v6so6695456itj.4; Tue, 04 Sep 2018 14:05:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=PypNyxxUwRBszqw2G4nACmW0LX58vdtyH9xCNyrpAn4=; b=mwd8D1BF6su5Sy7q+3ULO2Av8C+LacdK0ed7P93WSykNnAEl6yh5/s9B7N2KUbOVCR FGoqvmLkcsQqhgk8zqWCPROMH1fdMuFGPaZr/D3npDQU3lqQN8fgBOlXlnh+ebhCB1+U PHJ+L1/XkkUvPqT9+l0g4TW8Cwa+tU17ZiEpo+FxVpZ/y/x3gxkfl7rwmocD4Dr6oN/M tt2wd4b1PYYUk5Lsekdsqw2fAMOHU2CoTlM/MNR/v8R1qtHE+drWE+COE0dInG5xgUqw /wbRUCda3b5zy9yh1rZ1hwHC7Dey5QQ7LjoMlc4ePVX190I93vGpPPX+tnirjj5Bp7dU TqBw== X-Gm-Message-State: APzg51CtgQXf1edBbGTK8Do+wMLzpGPKuFlMD4vwBX0fDz3AwYOg+gxV mlQeh32tP8xhdgo05W89HoaUebeL X-Google-Smtp-Source: ANB0VdbA5FbNlKJQ0Tvevvn5Zy4Fm4A+33qws1nCoON37HMnKZTewm98dO3ILFYxtDpkn7dTCy36Xg== X-Received: by 2002:a02:7123:: with SMTP id n35-v6mr24646358jac.91.1536095144576; Tue, 04 Sep 2018 14:05:44 -0700 (PDT) Received: from mail-it0-f54.google.com (mail-it0-f54.google.com. [209.85.214.54]) by smtp.gmail.com with ESMTPSA id i139-v6sm14093349ioa.26.2018.09.04.14.05.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Sep 2018 14:05:44 -0700 (PDT) Received: by mail-it0-f54.google.com with SMTP id h20-v6so6703275itf.2; Tue, 04 Sep 2018 14:05:44 -0700 (PDT) X-Received: by 2002:a24:44d7:: with SMTP id o206-v6mr1654384ita.66.1536095144075; Tue, 04 Sep 2018 14:05:44 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:9542:0:0:0:0:0 with HTTP; Tue, 4 Sep 2018 14:05:43 -0700 (PDT) In-Reply-To: <1942661439.20180904235514@serebryakov.spb.ru> References: <609400979.20180904230820@serebryakov.spb.ru> <1942661439.20180904235514@serebryakov.spb.ru> From: Conrad Meyer Date: Tue, 4 Sep 2018 14:05:43 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: newfs silently fails if random is not ready (?) To: Lev Serebryakov Cc: FreeBSD Current , freebsd-fs , Xin LI Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Sep 2018 21:05:46 -0000 Hi Lev, On Tue, Sep 4, 2018 at 1:55 PM, Lev Serebryakov 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