Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2937931yba; Mon, 6 May 2019 14:11:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqzoY+p0+lRQAbyDuDOZO8GwSGtSCJrLqFNoXruMZBblDUX9RwHsqdh2XJgkhYqzDPQWoVVs X-Received: by 2002:a63:931c:: with SMTP id b28mr3420182pge.182.1557177077287; Mon, 06 May 2019 14:11:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557177077; cv=none; d=google.com; s=arc-20160816; b=cL5o5r6jYlJ32TOIl9fLuyBT3EiFuvJ5A4i01vXV+hqqpuxrMmp42t7wHXv5H5HVgv N+uUIwzldRWj5ZSKvWbQRQKr55vbzLrQrg/32j7mHD0IWUm8OiXjDLD2ujgnGWiLtG+3 wduPjDtSdb5IM5W2+fah9cEF6UmBllBcMRrkTG6bi0eIPK29Qf8j0DAQQouN0MKeJo+o czBK9cfbLfgW33iEoITBOlEFyMtxA3/6rbNzjbqMerXpIJ4cEbj0ZJ8tinaWTo1F3DDF kPtvT/Ut1agJesWb6kfVqbuFlKbqg/UEThzDCvNFSSIA68zKI28XfgTwqS+zb21LzNX8 7pYQ== 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=8bHpgQyzNXmSigtHpLPdMgiBL3zjoqHtCMHUPQ65vlc=; b=ULq55t2wFn5EJF7ulp0g7GvCuywuTD64AGC3NrdlueR5QyU0ux51m8HW293QjwncVt BGCBsE4PlMhX2Ex4mYVLd8Fh1/8LmlVLMcHCzUioonpD2/D0yeQyLsdawXmu8u8f18FV WjMRwFO7OS2Cg/7jfckQGnB8h3/OJd7/Bq12h2WPhxiNkQNzdJGn7Qk8q2ie8rezefqc 8TIwDZAcTYzM8EnlbFmjvSQQ8i5pR0Hc0y62Bwg/KVMZzOCoPlidzNUXzpfnWiYgbrpw vleHYMW5vaHkfsQhxNJf88BYKR2JNOQaH+jDh9X65QvlW74tks6xRAVI65MzAYa/VdUu dWXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=efbGg26t; 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 x21si17840094pgj.351.2019.05.06.14.11.00; Mon, 06 May 2019 14:11:17 -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=efbGg26t; 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 S1726476AbfEFVKL (ORCPT + 99 others); Mon, 6 May 2019 17:10:11 -0400 Received: from mail-ua1-f67.google.com ([209.85.222.67]:41322 "EHLO mail-ua1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726118AbfEFVKL (ORCPT ); Mon, 6 May 2019 17:10:11 -0400 Received: by mail-ua1-f67.google.com with SMTP id s30so5208565uas.8 for ; Mon, 06 May 2019 14:10:10 -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=8bHpgQyzNXmSigtHpLPdMgiBL3zjoqHtCMHUPQ65vlc=; b=efbGg26t1plscKmTr5AG/RpzJ3Ly5HJYzat+OL5lpECeRe1if/gjdAvwM+3ktU48Ud FmojR3dM0QW0g9CApczD3ijClH8YvAj9cTzAqrmcZ0tq90TckGXajrvoaa1RrzTz9rR/ tjoKcGH8AkqVNdaJKEU9GZYqZp4DICTTtYSnM= 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=8bHpgQyzNXmSigtHpLPdMgiBL3zjoqHtCMHUPQ65vlc=; b=GERRpCzQY0qIkEz0IdIFTehXEpXz+stmu3xOJPvmz0V7uYwxvNLA5XZEab9Efhjtjl VHGUqRqn5J+HiZFD9/xbh/XiWHp8eSXxi35eII91DTMu7Qyh/u32cf2HVG5PDWBZqivg vG7lB5Bqc79tvN5xnCGHuzK4KI+EzPWqxn1adhWJcu0wWcUeIP8y+TzcHMbAmYXwcWPJ EvHhAGuMyGado6z2+CAVBTjzzQOSyx/rpYtesFf84JD8kEDUhaQhPh+NX1czRvPHP4JT LhobkSTCK1fBcSXkTUV5VFSHaXrckDt8agxD3qzYusbOmhD/gWK4XhU0gVC7f8rxzdqe JJOQ== X-Gm-Message-State: APjAAAWLcGc1eZlZMU8CRtVirJs9ccxSAKduDXruUuEA+hGl1dp/Zljc 81DChEJaRy2JQONN0sBXsPEkIt1AHWM= X-Received: by 2002:ab0:70d4:: with SMTP id r20mr12008901ual.67.1557177009060; Mon, 06 May 2019 14:10:09 -0700 (PDT) Received: from mail-vs1-f44.google.com (mail-vs1-f44.google.com. [209.85.217.44]) by smtp.gmail.com with ESMTPSA id 15sm1923057vkg.16.2019.05.06.14.10.07 for (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Mon, 06 May 2019 14:10:08 -0700 (PDT) Received: by mail-vs1-f44.google.com with SMTP id e2so9030041vsc.13 for ; Mon, 06 May 2019 14:10:07 -0700 (PDT) X-Received: by 2002:a67:f849:: with SMTP id b9mr9084650vsp.188.1557177007238; Mon, 06 May 2019 14:10:07 -0700 (PDT) MIME-Version: 1.0 References: <20190503174730.245762-1-dianders@chromium.org> In-Reply-To: <20190503174730.245762-1-dianders@chromium.org> From: Kees Cook Date: Mon, 6 May 2019 14:09:55 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] pstore/ram: Improve backward compatibility with older Chromebooks To: Douglas Anderson , Rob Herring Cc: Anton Vorontsov , linux-rockchip@lists.infradead.org, jwerner@chromium.org, Guenter Roeck , Matthias Kaehlcke , Brian Norris , Colin Cross , Tony Luck , LKML 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 From: Douglas Anderson Date: Fri, May 3, 2019 at 10:48 AM To: Kees Cook, Anton Vorontsov Cc: , , , , , Douglas Anderson, Colin Cross, Tony Luck, > When you try to run an upstream kernel on an old ARM-based Chromebook > you'll find that console-ramoops doesn't work. > > Old ARM-based Chromebooks, before > ("ramoops: support upstream {console,pmsg,ftrace}-size properties") > used to create a "ramoops" node at the top level that looked like: > > / { > ramoops { > compatible = "ramoops"; > reg = <...>; > record-size = <...>; > dump-oops; > }; > }; > > ...and these Chromebooks assumed that the downstream kernel would make > console_size / pmsg_size match the record size. The above ramoops > node was added by the firmware so it's not easy to make any changes. > > Let's match the expected behavior, but only for those using the old > backward-compatible way of working where ramoops is right under the > root node. > > NOTE: if there are some out-of-tree devices that had ramoops at the > top level, left everything but the record size as 0, and somehow > doesn't want this behavior, we can try to add more conditions here. > > Signed-off-by: Douglas Anderson I like this; thanks! Rob is this okay by you? I just want to double-check since it's part of the DT parsing logic. I'll pick it up and add a Cc: stable. -Kees > --- > > fs/pstore/ram.c | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c > index c5c685589e36..8df3bfa2837f 100644 > --- a/fs/pstore/ram.c > +++ b/fs/pstore/ram.c > @@ -669,6 +669,7 @@ static int ramoops_parse_dt(struct platform_device *pdev, > struct ramoops_platform_data *pdata) > { > struct device_node *of_node = pdev->dev.of_node; > + struct device_node *parent_node; > struct resource *res; > u32 value; > int ret; > @@ -703,6 +704,23 @@ static int ramoops_parse_dt(struct platform_device *pdev, > > #undef parse_size > > + /* > + * Some old Chromebooks relied on the kernel setting the console_size > + * and pmsg_size to the record size since that's what the downstream > + * kernel did. These same Chromebooks had "ramoops" straight under > + * the root node which isn't according to the upstream bindings. Let's > + * make those old Chromebooks work by detecting this and mimicing the > + * expected behavior. > + */ > + parent_node = of_get_parent(of_node); > + if (of_node_is_root(parent_node) && > + !pdata->console_size && !pdata->ftrace_size && > + !pdata->pmsg_size && !pdata->ecc_info.ecc_size) { > + pdata->console_size = pdata->record_size; > + pdata->pmsg_size = pdata->record_size; > + } > + of_node_put(parent_node); > + > return 0; > } > > -- > 2.21.0.1020.gf2820cf01a-goog > -- Kees Cook