linux-kernel - Re: [Xen-devel] [PATCH] Fixes to Xen pcifront and pciback (v1)

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-next>] [day] [month] [year] [list]

Date:	Mon, 15 Feb 2016 14:35:56 +0000
From:	David Vrabel <david.vrabel@...rix.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	Tommi Airikka <tommi@...ikka.net>,
	<linux-kernel@...r.kernel.org>, <xen-devel@...ts.xenproject.org>,
	<david.vrabel@...rix.com>, <boris.ostrovsky@...cle.com>
Subject: Re: [Xen-devel] [PATCH] Fixes to Xen pcifront and pciback (v1)

On 11/02/16 21:10, Konrad Rzeszutek Wilk wrote:
> Hey,
> 
> These are patches that were developed for the Debian bug
> 810379 which san Tommi had openned.
> 
> The issue around from the two XSA fixes - which introduced
> this regression.

Applied to for-linus-4.6, thanks.

I rewrote some of the commit messages for clarity.  Please only put
relevant information in them and for regression fixes, make sure it's
clear what functionality regressed.

e.g. #1 now reads:

    Commit 408fb0e5aa7fda0059db282ff58c3b2a4278baa0 (xen/pciback: Don't
    allow MSI-X ops if PCI_COMMAND_MEMORY is not set) prevented enabling
    MSI-X on passed-through virtual functions, because it checked the VF
    for PCI_COMMAND_MEMORY but this is not a valid bit for VFs.

    Instead, check the physical function for PCI_COMMAND_MEMORY.

David