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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 28 May 2015 14:01:12 +0600
From:	Alexander Kuleshov <kuleshovmail@...il.com>
To:	Borislav Petkov <bp@...e.de>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Mark Rustad <mark.d.rustad@...el.com>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: [PATCH v8 0/3] x86/earlyprintk: setup serial earlyprintk as early
 as possible

2015-05-27 18:51 GMT+06:00 Borislav Petkov <bp@...e.de>:
> Now, have you tested this on real hardware? Because your 0/n message
> said "qemu" but I don't think that's sufficient. If we're going to
> enable early_printk this early, we'd need it working on real hardware
> too.
>
> For that I'd suggest adding a 4th, test patch which issues a couple of
> numbered early_printk() lines which we could run on a bunch of machines
> to see whether it actually works.

Thank you for suggestions. But how to do it? The patch already contains:

if (console_loglevel >= CONSOLE_LOGLEVEL_DEBUG)
      early_printk("Early printk is initialized\n");

But I've just noticesed that it does not print anything, because
console_loglevel can be CONSOLE_LOGLEVEL_DEBUG
only after parse_early_params too :) How to better be with it? To remove
if clause and just leave early_printk or something else?

Or you meant something else about patch for testing?
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ