linux-kernel - RE: [RFC] ACPI, APEI, Generic Hardware Error Source POLL/IRQ/NMI notification type support

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1292460306.12648.1207.camel@yhuang-dev>
Date:	Thu, 16 Dec 2010 08:45:06 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	Len Brown <lenb@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: RE: [RFC] ACPI, APEI, Generic Hardware Error Source POLL/IRQ/NMI
 notification type support

On Thu, 2010-12-16 at 00:40 +0800, Luck, Tony wrote:
> >Because the memory area used to transfer hardware error information
> >from BIOS to Linux can be determined only in NMI, IRQ or timer
> >handler, but general ioremap can not be used in atomic context, so a
> >special version of atomic ioremap is implemented for that.
> >
> >Known issue:
> >
> >- Error information can not be printed for recoverable errors notified
> >  via NMI, because printk is not NMI-safe. Will fix this via delay
> >  printing to IRQ context via irq_work or make printk NMI-safe.
> 
> Would it be possible to defer the "ioremap" to a work queue too? Then
> we wouldn't need the special versions of ioremap.

For recoverable error, we can defer the "ioremap" to a work queue,
because most recoverable action can take place only there in fact. But
for fatal error, I think it is too late to be processed in a work queue,
we need go panic as soon as possible to prevent data corruption.

Best Regards,
Huang Ying


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