linux-kernel - RE: VMware PCI passthrough regression

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

Date:	Fri, 12 Feb 2016 00:43:13 +0000
From:	Jason Taylor <jason.taylor@...plivity.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"x86@...nel.org" <x86@...nel.org>,
	Jiang Liu <jiang.liu@...ux.intel.com>
Subject: RE: VMware PCI passthrough regression

> Actually that is a 4.2 kernel according to the dmesg in the bug tracker.

It's both. I had reproduced on 4.4.

> The oops is a genuine driver bug probably unearthed by the irq issue. That should be reported seperately to the megasas folks.

Thanks, I sent an email to their list.

> - whether that kernel works on the real hardware with that LSI card
> - whether that kernel works in a KVM guest with that card passed through
> If one of those things break, we can certainly help to analyse that. If not, then you need to talk to vmware.

Works fine on real hardware and KVM. Filed an issue with VMware and the fix is in the works.

Jason
---------------------------------------------------------------------------------------
PRIVACY STATEMENT:
This message is a PRIVATE communication.  This message and all attachments are a private communication sent by SimpliVity and are considered to be confidential or protected by privilege. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the information contained in or attached to this message is strictly prohibited.  Please notify the sender of the delivery error by replying to this message, and then delete it from your system.
---------------------------------------------------------------------------------------