linux-kernel - Re: [PATCH] mptfusion: enable no_write_same in scsi_host

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]

Message-ID: <20140922181929.GA11319@infradead.org>
Date:	Mon, 22 Sep 2014 11:19:29 -0700
From:	Christoph Hellwig <hch@...radead.org>
To:	Chris J Arges <chris.j.arges@...onical.com>
Cc:	Christoph Hellwig <hch@...radead.org>, linux-scsi@...t.kernel.org,
	bruce.lucas@...godb.com,
	Nagalakshmi Nandigama <nagalakshmi.nandigama@...gotech.com>,
	Praveen Krishnamoorthy <praveen.krishnamoorthy@...gotech.com>,
	Sreekanth Reddy <sreekanth.reddy@...gotech.com>,
	Abhijit Mahajan <abhijit.mahajan@...gotech.com>,
	MPT-FusionLinux.pdl@...gotech.com, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mptfusion: enable no_write_same in scsi_host_template

On Mon, Sep 22, 2014 at 01:17:01PM -0500, Chris J Arges wrote:
> > 
> I've only been able to reproduce this on VMWare. There is a pretty
> straightforward reproducer in the BugLink if there is any interest in
> verifying on hardware.
> 
> How would you recommending blacklisting only VMWare guests in this case?

Can you check what PCI subdevice and subvendor IDs the device you can
reproduce it with have?  If the subvendor is Vmware that would be easy,
if not the Avago people might be able to help with a device specific
VMware identification.  If that fails we have kernel helpers to
identify the hypervisor, but I'd rather avoid that as it would also
trigger for PCI pass through devices.

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