From: Kees Cook <keescook@chromium.org>
To: Vijay Balakrishna <vijayb@linux.microsoft.com>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Anton Vorontsov <anton@enomsg.org>,
linux-kernel@vger.kernel.org
Subject: Re: pstore/ram: printk: NULL characters in pstore ramoops area
Date: Thu, 10 Aug 2023 20:05:40 -0700 [thread overview]
Message-ID: <202308102001.55158F519@keescook> (raw)
In-Reply-To: <0dace822-ce13-906e-46bd-e1cb9274cafe@linux.microsoft.com>
On Thu, Aug 10, 2023 at 05:48:17PM -0700, Vijay Balakrishna wrote:
> On 8/10/23 16:50, Kees Cook wrote:
> > Can you share the .config you're building with? And what are you using
> > to trigger an Oops? I will see if I can reproduce this...
>
> Config: https://paste.ubuntu.com/p/Vrcsf8Ry9g/
Thanks! I'll see how close I can get to this for my local testing...
>
> Just ran plain "sudo reboot" and inspected /var/lib/systemd/pstore/dmesg-ramoops-0 after reboot.
If you have a "dmesg-ramoops-0" there, something Oopsed. On a clean
shutdown, only "console-ramoops-0" will be recorded. Can you double
check by deleting everything in /var/lib/systemd/pstore/ and rebooting?
If you still get a dmesg-ramoops-0 file, can you upload that somewhere
so I can look at it?
Also, can you send the contents of /proc/iomem ?
--
Kees Cook
next prev parent reply other threads:[~2023-08-11 3:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f28990eb-03bc-2259-54d0-9f2254abfe62@linux.microsoft.com>
2023-08-04 7:59 ` pstore/ram: printk: NULL characters in pstore ramoops area Kees Cook
2023-08-10 23:32 ` Vijay Balakrishna
2023-08-10 23:50 ` Kees Cook
2023-08-11 0:48 ` Vijay Balakrishna
2023-08-11 3:05 ` Kees Cook [this message]
2023-08-11 3:16 ` Kees Cook
2023-08-07 17:19 ` Vijay Balakrishna
2023-08-08 8:15 ` Petr Mladek
2023-08-09 1:21 ` Vijay Balakrishna
2023-08-10 9:14 ` Petr Mladek
2023-08-11 5:23 ` 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=202308102001.55158F519@keescook \
--to=keescook@chromium.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tony.luck@intel.com \
--cc=vijayb@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.