linux-kernel - Re: [PATCH] quirks: Flag up and handle the AMD 8151 Errata #24

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: <1158086743.6780.86.camel@localhost.localdomain>
Date:	Tue, 12 Sep 2006 19:45:43 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andi Kleen <ak@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] quirks: Flag up and handle the AMD 8151 Errata #24

Ar Maw, 2006-09-12 am 17:29 +0200, ysgrifennodd Andi Kleen:
> If the system really locks up afterwards they will likely never see it though? 

They'll see it at boot.

> I just don't think the printk will that useful and if it locks up people will
> blame Linux anyways even with printk.

Which is why I also intend to make sure the drivers aren't defaulting to
ignore but all do it properly and require a force flag. PCIPCI_FAIL
means it doesn't work. No driver should be ignoring that flag.
> 
> > And "all that code" is a single quirk (which I think can be __init as
> > you can't get a hotplug bridge) and updated logic checks which my gcc
> > generates the same amount of code for as it did previously.
> >
> > All what code ?
> 
> Well it was a large change.

You must use a bigger font than I do ;)

Alan

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