linux-kernel - Re: [PATCH] mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0

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:	Mon, 15 Dec 2014 14:23:37 +0100
From:	Johannes Thumshirn <johannes.thumshirn@....de>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>,
	Andreas Werner <andreas.werner@....de>,
	<linux-kernel@...r.kernel.org>,
	Johannes Thumshirn <johannes.thumshirn@....de>
Subject: Re: [PATCH] mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0

On Tue, Oct 28, 2014 at 05:11:32PM +0100, Johannes Thumshirn wrote:
> Currently it is not possible to have a kernel with built-in MCB attached
> devices. This results out of the fact that mcb-pci requests PCI BAR 0, then
> parses the chameleon table and calls the driver's probe function before
> releasing BAR 0 again. When building the kernel with modules this is not a
> problem (and therefore it wasn't detected by my tests yet).
> 
> A solution is to only remap the 1st 0x200 bytes of a Chameleon PCI device.
> 0x200 bytes is the maximum size of a Chameleon v2 Table.
> 
> Also this patch stops disabling the PCI device on successful registration of MCB
> devices.
> 
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@....de>
> Suggested-by: Bjorn Helgaas <bhelgaas@...gle.com>

Hi Greg,

Is there any specific reason why you didn't pick this one up for 3.19? Or did it
just got lost in your queue?

Thanks,
	Johannes

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