linux-kernel - Re: [Xen-devel] [PATCH v5] Fixes to Xen pciback for 3.17.

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:	Tue, 5 Aug 2014 10:44:38 +0200
From:	Sander Eikelenboom <linux@...elenboom.it>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC:	David Vrabel <david.vrabel@...rix.com>, gregkh@...uxfoundation.org,
	<boris.ostrovsky@...cle.com>, <linux-kernel@...r.kernel.org>,
	<xen-devel@...ts.xenproject.org>
Subject: Re: [Xen-devel] [PATCH v5] Fixes to Xen pciback for 3.17.

Monday, August 4, 2014, 8:43:18 PM, you wrote:

> On Fri, Aug 01, 2014 at 04:30:05PM +0100, David Vrabel wrote:
>> On 14/07/14 17:18, Konrad Rzeszutek Wilk wrote:
>> > Greg: goto GHK
>> > 
>> > This is v5 version of patches to fix some issues in Xen PCIback.
>> 
>> Applied to devel/for-linus-3.17.

> Thank you.
>> 
>> I dropped the stable Cc for #2 pending a final decision on whether it
>> really is a stable candidate.

> OK.
>> 
>> David

Hi Konrad / David,

This series still lacks a resolution on the sysfs /do_flr /reset,
as a result the pci devices are not reset after shutdown of a guest.
(no more pciback 0000:xx:xx.x: restoring config space at offset xxx)

So this series now introduces a regression to 3.16, which causes devices to malfunction 
after a guest reboot or after assigning the devices to another guest.

Apart from that .. i can't resist to remind the other issue with removing pci
devices passed through to HVM guests related to the signaling via xenstore,
described in:

http://lists.xen.org/archives/html/xen-devel/2014-07/msg01875.html 

--
Sander

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