public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Tony Luck <tony.luck@intel.com>
Cc: Matt Fleming <matt@console-pimps.org>,
	linux-efi <linux-efi@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: df36ac1bc2a16 ("pstore: Don't allow high traffic options on fragile devices")
Date: Thu, 10 Apr 2014 20:15:03 +0200	[thread overview]
Message-ID: <20140410181503.GA4704@pd.tnic> (raw)

Hey Tony,

so I was wondering whether we could finally put that UEFI thing to use
and log dmesg into it but then Matt pointed me to df36ac1bc2a16.

Even though those nvram devices are fragile and can only stomach a
limited amount of writes, wouldn't it be a nifty feature to have a
kernel cmdline param of the sort "put_dmesg_in_nvram_this_one_time_only"
which logs to nvram only once for debugging purposes.

The usecase I have in mind is all those laptops which are sporting UEFI
now and where logging to serial or netconsole or something else is
simply not an option, for whatever reason (I'm sure anyone can think of
a number of those). If we had this, it would be one step closer to the
holy grail of being able to catch dmesg even on laptops.

We could also add checks like if efivarfs already has a dump-type* file
to not log, etc etc. Eventually, it would be a user decision whether to
still log to nvram or not, i.e. brick her laptop or not.

Thoughts?

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

             reply	other threads:[~2014-04-10 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 18:15 Borislav Petkov [this message]
2014-04-10 18:34 ` df36ac1bc2a16 ("pstore: Don't allow high traffic options on fragile devices") Luck, Tony
2014-04-10 18:57   ` Borislav Petkov

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=20140410181503.GA4704@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.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