All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "Tony Luck" <tony.luck@intel.com>,
	"Colin Cross" <ccross@android.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Anton Vorontsov" <anton@enomsg.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Kees Cook <keescook@chromium.org>,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] pstore/ftrace: add a kernel parameter to start pstore recording
Date: Thu, 18 Nov 2021 10:08:38 -0800	[thread overview]
Message-ID: <163725891549.1179817.6546871118396864090.b4-ty@chromium.org> (raw)
In-Reply-To: <20210610082134.20636-1-u.kleine-koenig@pengutronix.de>

On Thu, 10 Jun 2021 10:21:34 +0200, Uwe Kleine-König wrote:
> With this knob you can enable pstore recording early enough to debug
> hangs happening during the boot process before userspace is up enough to
> enable it via sysfs.
> 
> 

I refactored this patch a fair bit so it would use a common enable/disable
routine, but otherwise the original intent remains. :)

Applied to for-next/pstore, thanks!

[1/1] pstore/ftrace: add a kernel parameter to start pstore recording
      https://git.kernel.org/kees/c/8d74118c9441

-- 
Kees Cook


  parent reply	other threads:[~2021-11-18 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10  8:21 [PATCH] pstore/ftrace: add a kernel parameter to start pstore recording Uwe Kleine-König
2021-11-16 17:06 ` Steven Rostedt
2021-11-16 17:28   ` Uwe Kleine-König
2021-11-16 17:37     ` Steven Rostedt
2021-11-16 20:52       ` Uwe Kleine-König
2021-11-16 21:00       ` Kees Cook
2021-11-29 22:40         ` Steven Rostedt
2021-11-18 18:08 ` Kees Cook [this message]
2021-11-18 18:31   ` Kees Cook
2021-11-19  7:25     ` Uwe Kleine-König

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=163725891549.1179817.6546871118396864090.b4-ty@chromium.org \
    --to=keescook@chromium.org \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tony.luck@intel.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.