linux-kernel - Re: [PATCH v3] mptfusion: enable no_write

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: <yq14mvxudbv.fsf@sermon.lab.mkp.net>
Date:	Tue, 23 Sep 2014 19:28:04 -0400
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Chris J Arges <chris.j.arges@...onical.com>
Cc:	hch@...radead.org, bruce.lucas@...godb.com,
	adam.radford@...gotech.com, kashyap.desai@...gotech.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 v3] mptfusion: enable no_write_same for vmware scsi disks

>>>>> "Chris" == Chris J Arges <chris.j.arges@...onical.com> writes:

Chris> 1) Does this workaround make sense? Perhaps there is an easier
Chris>    way?

One option is to ship a udev rule that disables write same on VMware
disks. However, I don't have a fundamental problem having a workaround
for this in the kernel.

Chris> 2) Do we expect changing max_write_same_blocks at the scsi_disk
Chris>    level to propagate the right write_same flags to other layers
Chris>    such as dm?

No, there's currently no way to communicate that the underlying topology
has changed.

-- 
Martin K. Petersen	Oracle Linux Engineering
--
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/