From: Kees Cook <keescook@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: Kees Cook <keescook@chromium.org>,
Joel Fernandes <joel@joelfernandes.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>
Subject: [PATCH -next v2 06/12] pstore/ram: Report backend assignments with finer granularity
Date: Thu, 29 Nov 2018 15:08:35 -0800 [thread overview]
Message-ID: <20181129230841.29955-7-keescook@chromium.org> (raw)
In-Reply-To: <20181129230841.29955-1-keescook@chromium.org>
In order to more easily perform automated regression testing, this
adds pr_debug() calls to report each prz allocation which can then be
verified against persistent storage. Specifically, seeing the dividing
line between header, data, any ECC bytes. (And the general assignment
output is updated to remove the bogus ECC blocksize which isn't actually
recorded outside the prz instance.)
Signed-off-by: Kees Cook <keescook@chromium.org>
---
fs/pstore/ram.c | 4 ++--
fs/pstore/ram_core.c | 6 ++++++
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index 768759841491..10ac4d23c423 100644
--- a/fs/pstore/ram.c
+++ b/fs/pstore/ram.c
@@ -853,9 +853,9 @@ static int ramoops_probe(struct platform_device *pdev)
ramoops_pmsg_size = pdata->pmsg_size;
ramoops_ftrace_size = pdata->ftrace_size;
- pr_info("attached 0x%lx@0x%llx, ecc: %d/%d\n",
+ pr_info("using 0x%lx@0x%llx, ecc: %d\n",
cxt->size, (unsigned long long)cxt->phys_addr,
- cxt->ecc_info.ecc_size, cxt->ecc_info.block_size);
+ cxt->ecc_info.ecc_size);
return 0;
diff --git a/fs/pstore/ram_core.c b/fs/pstore/ram_core.c
index f5d0173901aa..62830734deee 100644
--- a/fs/pstore/ram_core.c
+++ b/fs/pstore/ram_core.c
@@ -576,6 +576,12 @@ struct persistent_ram_zone *persistent_ram_new(phys_addr_t start, size_t size,
if (ret)
goto err;
+ pr_debug("attached %s 0x%zx@0x%llx: %zu header, %zu data, %zu ecc (%d/%d)\n",
+ prz->label, prz->size, (unsigned long long)prz->paddr,
+ sizeof(*prz->buffer), prz->buffer_size,
+ prz->size - sizeof(*prz->buffer) - prz->buffer_size,
+ prz->ecc_info.ecc_size, prz->ecc_info.block_size);
+
return prz;
err:
persistent_ram_free(prz);
--
2.17.1
next prev parent reply other threads:[~2018-11-29 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 23:08 [PATCH -next v2 00/12] pstore: various clean-ups Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 01/12] pstore/ram: Correctly calculate usable PRZ bytes Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 02/12] pstore: Do not use crash buffer for decompression Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 03/12] pstore: Remove needless lock during console writes Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 04/12] pstore: Avoid duplicate call of persistent_ram_zap() Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 05/12] pstore/ram: Standardize module name in ramoops Kees Cook
2018-11-29 23:08 ` Kees Cook [this message]
2018-11-29 23:08 ` [PATCH -next v2 07/12] pstore/ram: Add kern-doc for struct persistent_ram_zone Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 08/12] pstore: Improve and update some comments and status output Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 09/12] pstore: Replace open-coded << with BIT() Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 10/12] pstore: Map PSTORE_TYPE_* to strings Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 11/12] pstore/ram: Simplify ramoops_get_next_prz() arguments Kees Cook
2018-11-29 23:08 ` [PATCH -next v2 12/12] pstore/ram: Do not treat empty buffers as valid Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181129230841.29955-7-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).