linux-kernel - Re: FW/BIOS Bug category for oops.kernel.org

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: <20141103213442.GB27387@pd.tnic>
Date:	Mon, 3 Nov 2014 22:34:43 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	arapov@...il.com, poros@...hat.com,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, matt@...sole-pimps.org
Subject: Re: FW/BIOS Bug category for oops.kernel.org

On Mon, Nov 03, 2014 at 10:26:10PM +0100, Peter Zijlstra wrote:
> Hi oops.kernel.org folks,
> 
> I'm wanting to collect information on FW/BIOS bugs, and I figured that
> we could use the oops.kernel.org infrastructure to do this.
> 
> Now, I'd prefer to not use the regular BUG/WARN because it might confuse
> users and the stacktrace is entirely pointless -- we know were/why we
> generate the msgs.
> 
> Is everything between:
> 
>         pr_warn("------------[ cut here ]------------\n");
> and:
>         pr_warn("---[ end trace %016llx ]---\n", (unsigned long long)oops_id);
> 
> sucked in automagically, or do we need more magic?

Btw, we have FW_{BUG,WARN,INFO} macros for exactly firmware issues.

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