linux-kernel - df36ac1bc2a16 ("pstore: Don't allow high traffic options on fragile devices")

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Apr 2014 20:15:03 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Tony Luck <tony.luck@...el.com>
Cc:	Matt Fleming <matt@...sole-pimps.org>,
	linux-efi <linux-efi@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: df36ac1bc2a16 ("pstore: Don't allow high traffic options on fragile
 devices")

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.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/