Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp1710075ybi; Sun, 30 Jun 2019 22:30:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqyXtbZ5nadwd1/uMllYdHHVwdGJqCEHfUte+ZmbvuSCqy12lQPyeX4g44lkJblKHokRN0mZ X-Received: by 2002:a63:e90b:: with SMTP id i11mr23093799pgh.351.1561959057935; Sun, 30 Jun 2019 22:30:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561959057; cv=none; d=google.com; s=arc-20160816; b=T6ThTiH71dxVyf6y8G5JJnlWkaB2qMsMLzGREwA100FAFipzhI33dB05k0Ymm4q1kk jFFf8TP1Gf/B1kSoMnSgNcLD8YYGM6r+IRbsydB5clmXJrG92IgPRyWnWwRS5YTWJtLr Pdl81VZYKIm0bbMJxBMk7dSlHyBnZRbVEKwfWYv0SeIOZ4ComZgFxgcvSa8oP1T/sqQ+ WJsJNJqaOBohY3LpVXMdTlKiDG4MHcmzNrt6QGGgXFl7exD0P9JA0H2oj5qCoRBAkY56 xyLAx5WRZa966bYjobef2eZuv6CJXCxobSAAd4R7Rxi/UfmDAypdCuSaCpS0lHyZViCj cKeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=j4LijnemKoLKQMl/B23h/AFjsTibtIxnLw1/ziD/okk=; b=iCq7njZ+N24vosa/CNbItrqDCENTX/5G/gt3fsvnV5bpnXAu1zOvxUYOEl04NHK/FV DskwZscDweUDPtHUQf4AC2Pqykjs89BbeMzzezR1ah38cMvqN9dqlDrYkr/EDcjZQ2t2 gqnCFEU4m7ky4xU2ykVaR/Z94fGYr8+R8Zogr4t9tvXKQvnXK2BSsTpxfyJhPW35g9wm G+hF6lHEfAXCIhTpGTKiBkuDbXmMbmQpKybGQ3WYAePfza7XDO585Px9VxkphteGRWQx HLamqI3F2meatzQuZTQplWxw55gJiYsw4pTvthZkvVJ4yO2ISj6jb5DBoqj4Ttw6cp5M huIQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=YVFFkZJj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 186si8320565pgc.248.2019.06.30.22.30.42; Sun, 30 Jun 2019 22:30:57 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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=@chromium.org header.s=google header.b=YVFFkZJj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727176AbfGAEeD (ORCPT + 99 others); Mon, 1 Jul 2019 00:34:03 -0400 Received: from mail-qt1-f194.google.com ([209.85.160.194]:39505 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726869AbfGAEeD (ORCPT ); Mon, 1 Jul 2019 00:34:03 -0400 Received: by mail-qt1-f194.google.com with SMTP id i34so13257169qta.6 for ; Sun, 30 Jun 2019 21:34:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j4LijnemKoLKQMl/B23h/AFjsTibtIxnLw1/ziD/okk=; b=YVFFkZJj/CNI+ghOb+Ya0Nzz514913rZbQ1YwSPyXWJG0iedMSqToFMHZSnvnPuPT0 O8cxNkk5ThpOsJF6gBM/kMDq+25cqP4doJFO4stISlZcxnEC15ROlJ6RTv+tUb36RMUP oJiNOHbUBSYf7k9M2h1kSEXdcBrPmOJGKebzY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j4LijnemKoLKQMl/B23h/AFjsTibtIxnLw1/ziD/okk=; b=gN2IW6dPviHTo72TR5D4JuCBigjs+A0pFP9pA1tryHvr8TSpssn3Ym9GdAKBofh1sh ZDkadzM8TQrOMGZCWcU/XKRml33i0xZ03RS79R14SLOYUHCS20xHpGGb9OT+DZEIZ4bZ IJkSTebcsOdJIgF3WCRpVxDJARi/TOnFl512Uy9r1tLU2I5x1xF4KpLs1vYRyn55kiac 4mBXkgrb2H4V3Zxa9tg4DvfrEPWirsx3i8CnGS/D5GMp6sJuKM7nOS9t2e8gk1ba7znK a+r5oF0VtOI+lTHJ9YWpvsAJ893RfLijG7HPcr1Gi++nd4iw3puaxoBChg1//okTf85p Uo+Q== X-Gm-Message-State: APjAAAU+0fFjedUPs+yzWQ3FQyo/TSHphXNoI8MszSeA0ja6MGsxiAu8 1vdUEPPRwjmPNlghLSKWD1IEGXVu6FIFOZL1UlV0PA== X-Received: by 2002:ac8:4601:: with SMTP id p1mr18877187qtn.181.1561955642169; Sun, 30 Jun 2019 21:34:02 -0700 (PDT) MIME-Version: 1.0 References: <20190612043258.166048-1-hsinyi@chromium.org> <20190612043258.166048-4-hsinyi@chromium.org> <20190628094251.GC36437@lakrids.cambridge.arm.com> In-Reply-To: From: Hsin-Yi Wang Date: Mon, 1 Jul 2019 12:33:36 +0800 Message-ID: Subject: Re: [PATCH v6 3/3] arm64: kexec_file: add rng-seed support To: Mark Rutland Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Rob Herring , devicetree@vger.kernel.org, lkml , Frank Rowand , Catalin Marinas , Will Deacon , Andrew Morton , Mike Rapoport , Ard Biesheuvel , Miles Chen , James Morse , Andrew Murray , Jun Yao , Yu Zhao , Robin Murphy , Laura Abbott , Stephen Boyd , Kees Cook Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 28, 2019 at 7:47 PM Hsin-Yi Wang wrote: > > > > If the RNG wasn't initialised, we'd carry on with a warning. Why do we > > follow a different policy here? > > (Sorry, please ignore previous comment) I think this part should be same as kaslr, since they are both adding random seeds: If RNG isn't initialized, we won't be able to set these seeds, and dtb can't do anything else to deal with this, so carry on with warning. If fdt_setprop failed with no space, create_dtb() will try to setup dtb again with more space. Other failures are setting fdt's error, so returns invalid.