Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp6394336ybe; Wed, 18 Sep 2019 02:45:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqw5RSotc9sv0yDJc4doF8falVF2jkmfadWg2DmKwJzoOZYK36uBuv54Piz3etGNEZ/GcxPA X-Received: by 2002:aa7:d883:: with SMTP id u3mr7480672edq.281.1568799952377; Wed, 18 Sep 2019 02:45:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568799952; cv=none; d=google.com; s=arc-20160816; b=os8URpufA4IpQsgBFECYLrSos8ht5lOIZlQW0qUpe486rrSlAo0ovr9qb3OHwfQ3u8 9dwvCaSTYfN7bQVS7fZMRb8BXfnz0IBdyVDPraBX/JMJyfTBKAjuEbh2RLvRczq0cNpg XW/bOu/11Vn1tsXsvpJXt+CT44MbXMwuNIvLkj+GaJ83xiZkcwqOxnB9ydKZEG1hjrRr U/qJmLXOEXDitsRjlF28Z4jU7QuGUxpg/O3v8B2GkKd56qXs/gM3Cu3VQHJc/QUrK12f 6jhPvhvVYra10uv9I+v6ZujpAMEMrXbFdvkKnTAuN9i4gs6XVTadvnhnYKVzxtw4bvlP a11Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=oVhNis/dF5C/JXuxrb6BPz9PriRAlEp0NTIbkhZyp5o=; b=w5jCRa+OFQsVclnlNFCLCrQdqtNqTvb1x4NT7IUnfnakgjjR4aR2JRh0UbUjzjhuRr qrxirFcsqgXgJO2sAlOqBBRfKr37HEnbkvuyePqSnm8nbA2ZtX014wH1RCMldkDovF+y Hpx+f3ERD1+auUKjkFTTAC2aejQ2aYIAcCeYVHqCDOgxCAdtBLYhovzwmYZ32Ov8zlun zCuCoqbdcT3+reZDOs8SakFLmxUm2XNHVkbOc/3vN1jlxcJRYZyd1UyL2zIOdk1iIynw SUXrzXfuqLZ2v0EWTaFLNH+lycyL1mWbac51Kvq6OXqYE0zkmt76DqinKF4Db1I5e9rL 8CfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@rasmusvillemoes.dk header.s=google header.b=B8nbCdz6; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u6si2623524eds.173.2019.09.18.02.45.22; Wed, 18 Sep 2019 02:45:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@rasmusvillemoes.dk header.s=google header.b=B8nbCdz6; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727616AbfIRJdo (ORCPT + 99 others); Wed, 18 Sep 2019 05:33:44 -0400 Received: from mail-lj1-f195.google.com ([209.85.208.195]:36827 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726818AbfIRJdn (ORCPT ); Wed, 18 Sep 2019 05:33:43 -0400 Received: by mail-lj1-f195.google.com with SMTP id v24so6520035ljj.3 for ; Wed, 18 Sep 2019 02:33:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rasmusvillemoes.dk; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=oVhNis/dF5C/JXuxrb6BPz9PriRAlEp0NTIbkhZyp5o=; b=B8nbCdz6S1ldEQ7bMIDaDYAD9/FFZKl5H5tbiDBQgmM5mtEzL5Cb++ud3waqdB5AvI S3Bt8fKcaZu1KgPR9x/Vr093cICdeFVV8pNrgQVbFj3uO36dphq6M9k5EED/V7cBmhZY mxM5PZXwLLiQmyK0n1Q9SyO0M587jTWg3fBvs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=oVhNis/dF5C/JXuxrb6BPz9PriRAlEp0NTIbkhZyp5o=; b=CjJhXC5KBCak6JsbsBo61rizydRWcoOGy5HGO12I+YkMQJDlAp4S0bFBnxFRNxFc0n ARSKrT7mOtNHcLBo5zdcEBDHRI9tEfaE1WKRJ1ZKyGBP9CxLxRsqvo0NAP7AsDbUCBnq aGIrxV5sPeH444KKL5FouQGcOINbqU0m2sxgFpf7LXxrBVFI8bBNW5zlPqcizpa+Cd9L wlq7EU3Jey/3fMfg+iPYrh/6cEyc+L9z4L7Z6ForLv8NdcEnKYxjd68crgP7iBHKrA43 Y1pzebdAcf6m4dntzKfSvhrUdz30K+dpvPLO1CP4w+t2D5Fp7xs6APVs3DUx6l4AUaDM wQVg== X-Gm-Message-State: APjAAAVXJwpcmaW+cjlArwYQXpT0JMYQtg+AuBCvAZvu2614yMyPBJPT YrhX4AYRaMujDRq+TTDW/hCF0A== X-Received: by 2002:a2e:5dc3:: with SMTP id v64mr1722222lje.118.1568799221748; Wed, 18 Sep 2019 02:33:41 -0700 (PDT) Received: from [172.16.11.28] ([81.216.59.226]) by smtp.gmail.com with ESMTPSA id f21sm1083158lfm.90.2019.09.18.02.33.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Sep 2019 02:33:41 -0700 (PDT) Subject: Re: Linux 5.3-rc8 To: Linus Torvalds , Lennart Poettering Cc: "Ahmed S. Darwish" , "Theodore Y. Ts'o" , Willy Tarreau , Matthew Garrett , Vito Caputo , Andreas Dilger , Jan Kara , Ray Strode , William Jon McCann , "Alexander E. Patrakov" , zhangjs , linux-ext4@vger.kernel.org, lkml References: <20190917052438.GA26923@1wt.eu> <2508489.jOnZlRuxVn@merkaba> <20190917121156.GC6762@mit.edu> <20190917123015.sirlkvy335crozmj@debian-stretch-darwi.lab.linutronix.de> <20190917160844.GC31567@gardel-login> <20190917174219.GD31798@gardel-login> From: Rasmus Villemoes Message-ID: <89aeae9d-0bca-2a59-5ce2-1e18f6479936@rasmusvillemoes.dk> Date: Wed, 18 Sep 2019 11:33:39 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On 17/09/2019 22.58, Linus Torvalds wrote: > Side note, and entirely unrelated to this particular problem, but > _because_ I was looking at the entropy init and sources of randomness > we have, I notice that we still don't use the ToD clock as a source. And unrelated to the non-use of the RTC (which I agree seems weird), but because there's no better place in this thread: How "random" is the contents of RAM after boot? Sure, for virtualized environments one probably always gets zeroed pages from the host (otherwise the host has a problem...), and on PCs maybe the BIOS interferes. But for cheap embedded devices with non-ECC RAM and not a lot of value-add firmware between power-on and start_kernel(), would it make sense to read a few MB of memory outside of where the kernel was loaded and feed those to add_device_randomness() (of course, doing it as early as possible, maybe first thing in start_kernel())? Or do the reading in the bootloader and pass on the sha256() in the DT/rng-seed property? A quick "kitchen-table" experiment with the board I have on my desk shows that there are at least some randomness to be had after a cold boot. Maybe this has already been suggested and rejected? Rasmus