linux-kernel - Re: [PATCH 1/3] Introduce interface to report BIOS bugs

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]

Message-ID: <48AC5668.2030203@linux.intel.com>
Date:	Wed, 20 Aug 2008 19:37:44 +0200
From:	Andi Kleen <ak@...ux.intel.com>
To:	Thomas Renninger <trenn@...e.de>
CC:	linux-kernel@...r.kernel.org, len.brown@...el.com,
	arjan@...ux.intel.com, bjorn.helgaas@...com,
	linux-acpi@...r.kernel.org,
	Christian Kornacker <ckornacker@...e.de>
Subject: Re: [PATCH 1/3] Introduce interface to report BIOS bugs

Thomas Renninger wrote:

I approve of the basic idea. Some nits in the implementation.

First shouted macros look ugly. Can you use something lower case
similar to dev_printk()?

> +
> +#define 	FW_EMERG	KERN_EMERG  /* System cannot boot */
> +#define 	FW_ALERT 	KERN_ALERT  /* Risk of HW or data damage, 
> +					       e.g. overheating, dmraid */
> +#define 	FW_CRIT 	KERN_CRIT   /* A major device is not functional
> +					       e.g. hpet, lapic, network... */
> +#define 	FW_ERR		KERN_ERR    /* A major device is not working
> +					       as expected, e.g. cpufreq stuck
> +					       to lowest freq, lowered
> +					       performance, increased power
> +					       consumption... */

These should probably have another string after the KERN_* severities appended
because KERN_* doesn't make it into the syslog log files or serial
console logs and you would lose the severity then.


> +config REPORT_FIRMWARE_BUGS
> +	bool "Report Firmware Bugs"
> +	default y
> +	help
> +	  This option will make the kernel print out all firmware bug messages
> +	  it finds. This especially is very useful on ACPI systems where
> +	  potentially a lot firmware bugs can happen and should be reported.
> +	  
> +	  Always say yes here unless memory really matters.

I don't think this should be a CONFIG.  If someone really wants to save
that much memory they can disable printk.

-Andi
--
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/