linux-kernel - Re: [GIT PULL] PCI fixes for v3.19

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]

Date:	Fri, 30 Jan 2015 12:18:11 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Tony Luck <tony.luck@...il.com>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Lucas Stach <l.stach@...gutronix.de>,
	Richard Zhu <Richard.Zhu@...escale.com>,
	Marek Kordik <kordikmarek@...il.com>,
	Alex Williamson <alex.williamson@...hat.com>,
	Andreas Hartmann <andihartmann@...enet.de>,
	Alexey Voronkov <zermond@...il.com>,
	David Airlie <airlied@...ux.ie>,
	Alex Deucher <alexander.deucher@....com>
Subject: Re: [GIT PULL] PCI fixes for v3.19

On Fri, Jan 30, 2015 at 12:01 PM, Tony Luck <tony.luck@...il.com> wrote:
> On Fri, Jan 30, 2015 at 8:56 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>> Tony, does the system work as it did before?  Is the only problem that
>> now we have more warnings than we did before?
>
> Yup - things seem to be working. Just have a bunch of new console messages.
>
> It seems that at least some of them are valid - the BIOS isn't describing some
> things that it should.  I don't think we need to re-apply code that
> used to paper
> over this problem. I can just add these to the list of "harmless" messages to
> ignore when running new kernels on this old machine.
>
> Or did I misunderstand some part of this thread?

Nope, I think the complaints about BARs 0 and 8 on bus 80 are
legitimate errors, and adding them to the list of "harmless" messages
is the right thing to do.

The ones complaining about BAR 6 (an option ROM) are the ones I'm more
concerned about.  There's no address space assigned to them, but I
don't think that indicates a firmware defect, and the message is sort
of cryptic, so I don't want to emit it more often than we have to.

But if ia64 is handling these ROMs the same way as x86, this is just
an opportunity for future improvement, and we don't need to do
anything right now.

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