Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2398320imu; Thu, 24 Jan 2019 12:05:10 -0800 (PST) X-Google-Smtp-Source: ALg8bN5LWa8nDIyrDdj7svPlZsTbDzfidoe4uB9kWwsvkXdbZsbHToMTigbt9Lrd+1ZssWj8STaP X-Received: by 2002:a63:cf48:: with SMTP id b8mr7359600pgj.17.1548360310493; Thu, 24 Jan 2019 12:05:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548360310; cv=none; d=google.com; s=arc-20160816; b=aJIOm63rM7fB7GIuMhBZV24GDiRBAvxwL0OX+uMwjh8HRfZvO7I/7pNaYoLlHHLa4+ 5i9tAtrJSts0CDNuHQtKBatswc3UI4h+PCTRhJTTx/b3bgp93VbWGoQKlaktZRyWw0OL ofX8iDYR6cumdcd7G0gSaeMyS0SKbXK9EmwEdSi3uDla6QrEGDtl+81me7AAAKR71Tug Zhd+hDq9wsQxSvdUDMqkrhxCVo5F+VLbcokuBpotxJ7ptc266oKfTk1bK1Wp0U0PzDMi a+99+H04hFUT3CNmGvmpmZaNMtN86oRkOy88kCWzOO0PSRi/vzuZztdQ1oCbUxAR9YU/ CCJQ== 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:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=UgcCq7D9Zz2aNbo79s83nA5u2rnJdUE4yz5UlOkMqHc=; b=mmlCthZ2giabGaWvXJJ7328Nlha4V+XEZYDSpKAlGalmUM4IQTNVFU0qbJspwt8djt O7LGIB4Fx+q9UgwSNv1ZzAORPvZY8WvSLXql8GpRTnColRI6AMr/m0Al2jG+wzMgmNfQ 7k5hWXEg+5VeI8djlXjxjwZq9TOI5w2gKmMvQuAfZliCyId5khQ8bVosu5OLcXHmdgje 14S0V8/gfghEcfzUsSH1yRc/12btFntitRBG5K7auqanJ1zJdcZQ1DF/hEU06EEyWw/T W0no54+wWnKwSyQ9BzePtbIIL2zHnNpaAQeFkPaeu0/dKL8VprvRssITZhT4VZA2H3a0 MNKQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Ck1naZoK; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h189si22429393pfc.211.2019.01.24.12.04.55; Thu, 24 Jan 2019 12:05:10 -0800 (PST) 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=@kernel.org header.s=default header.b=Ck1naZoK; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731693AbfAXTbp (ORCPT + 99 others); Thu, 24 Jan 2019 14:31:45 -0500 Received: from mail.kernel.org ([198.145.29.99]:59484 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731666AbfAXTbj (ORCPT ); Thu, 24 Jan 2019 14:31:39 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 97242218E2; Thu, 24 Jan 2019 19:31:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548358299; bh=+l333r3CBr0C4mXwxeVcL+abTZyONSL6JHvZYTkowi0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Ck1naZoKquY3winFkgA3ndMCSGHYCoggub0Up5+15uK0QtsR5KKUaCvOf0x3+0j2c Ceuu18DwE9sGkpia4CEgbHimmhTBABdPJmd8tPMydhopKsfahjiobOSJKyHRm8nMjk N54sfZgS6+n7ua1S6ZXECQE5xfkEgzEPMTJI9vOM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, "Joel Fernandes (Google)" , Kees Cook , Sasha Levin Subject: [PATCH 4.14 23/63] pstore/ram: Do not treat empty buffers as valid Date: Thu, 24 Jan 2019 20:20:12 +0100 Message-Id: <20190124190157.733940265@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190124190155.176570028@linuxfoundation.org> References: <20190124190155.176570028@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.14-stable review patch. If anyone has any objections, please let me know. ------------------ [ Upstream commit 30696378f68a9e3dad6bfe55938b112e72af00c2 ] The ramoops backend currently calls persistent_ram_save_old() even if a buffer is empty. While this appears to work, it is does not seem like the right thing to do and could lead to future bugs so lets avoid that. It also prevents misleading prints in the logs which claim the buffer is valid. I got something like: found existing buffer, size 0, start 0 When I was expecting: no valid data in buffer (sig = ...) This bails out early (and reports with pr_debug()), since it's an acceptable state. Signed-off-by: Joel Fernandes (Google) Co-developed-by: Kees Cook Signed-off-by: Kees Cook Signed-off-by: Sasha Levin --- fs/pstore/ram_core.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/fs/pstore/ram_core.c b/fs/pstore/ram_core.c index ecdb3baa1283..11e558efd61e 100644 --- a/fs/pstore/ram_core.c +++ b/fs/pstore/ram_core.c @@ -488,6 +488,11 @@ static int persistent_ram_post_init(struct persistent_ram_zone *prz, u32 sig, sig ^= PERSISTENT_RAM_SIG; if (prz->buffer->sig == sig) { + if (buffer_size(prz) == 0) { + pr_debug("found existing empty buffer\n"); + return 0; + } + if (buffer_size(prz) > prz->buffer_size || buffer_start(prz) > buffer_size(prz)) pr_info("found existing invalid buffer, size %zu, start %zu\n", -- 2.19.1