linux-kernel - Re: [PATCH] quiet MMCONFIG related printks

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: <200701020837.45016.jbarnes@virtuousgeek.org>
Date:	Tue, 2 Jan 2007 08:37:44 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Alan <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH] quiet MMCONFIG related printks

On Tuesday, January 2, 2007 2:36 am, Alan wrote:
> On Mon, 1 Jan 2007 21:01:38 -0800
>
> Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> > Using MMCONFIG for PCI config space access is simply an
> > optimization, not a requirement.  Therefore, when it can't be used,
> > there's no need for
>
> Some hardware reqires MCFG. In addition this is an error, a real
> error on the vendors part or ours and could indicate there are many
> other BIOS problems outstanding.

Ok, I was mistaken then.  However, I see this on several boxes, and the 
broken BIOSen out in the wild are unlikely to be fixed.  Maybe this 
should really be a KERN_WARNING instead since it may indicate that some 
devices will fail to work?

> We shouldn't keep quiet about serious errors in tables, we need
> people to know and be able to take appropriate action (eg new BIOSen,
> refusing certifications etc).

Ok.

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