Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <0abd4d8a-86cf-3697-584e-bfd313107ef9@huawei.com>
Date:   Tue, 19 Jul 2022 16:06:52 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.8.0
Subject: Re: Inquiry about the removal of flag O_NONBLOCK on /dev/random
Content-Language: en-US
To:     Eric Biggers <ebiggers@kernel.org>
CC:     <linux-crypto@vger.kernel.org>, <luto@kernel.org>, <tytso@mit.edu>,
        "Jason A. Donenfeld" <Jason@zx2c4.com>
References: <13e1fa9d-4df8-1a99-ca22-d9d655f2d023@huawei.com>
 <d49d35f5-8eaf-d5e8-7443-ac896a946db7@huawei.com>
 <YtYpQ1gf23mxIiYH@sol.localdomain>
From:   "Guozihua (Scott)" <guozihua@huawei.com>
In-Reply-To: <YtYpQ1gf23mxIiYH@sol.localdomain>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

> (I don't know why O_NONBLOCK stopped being recognized *before* the entropy pool
> has been initialized; it's either an oversight, or it was decided it doesn't
> matter.  Probably the latter, since I can't think of a real use case for using
> O_NONBLOCK on /dev/random.)

Does this mean that we expect all users of /dev/random to block until it 
is initialized?

-- 
Best
GUO Zihua