From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH] sd: always scan VPD pages if thin provisioning is enabled
Date: Wed, 25 Jan 2017 11:23:29 +0100 [thread overview]
Message-ID: <20170125102329.GA17657@lst.de> (raw)
In-Reply-To: <1485329165-64825-1-git-send-email-hare@suse.de>
On Wed, Jan 25, 2017 at 08:26:05AM +0100, Hannes Reinecke wrote:
> For any device with an older SCSI revision we might not
> be scanning VPD pages, which results in a wrongly configured
> discard mode if thin provisioned is enabled.
> According to sbc3 any thin provisioned device (ie devices which
> have the LBPME bit set in the output of READ CAPACITY(16)) need
> to support VPD pages. So this patch always enables VPD pages
> even for older SCSI revisions if thin provisioning is enabled.
Can you explain what you need this for? A device with a per-SBC3
revision that wants us to use UNMAP?
> + /*
> + * sbc3r36 states:
> + * The device server in a logical unit the supports
> + * logical block provisioning management shall support
> + * the Logical Block Provisioning VPD page.
> + * So VPD pages should be supported if lbpme is set.
> + */
It's a bit odd to quote SBC3 when the device clearly is pre-SBC3
to need this workaround..
> + if (!scsi_device_supports_vpd(sdp))
> + sdp->try_vpd_pages = 1;
Do the assignment unconditionally?
next prev parent reply other threads:[~2017-01-25 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 7:26 [PATCH] sd: always scan VPD pages if thin provisioning is enabled Hannes Reinecke
2017-01-25 7:57 ` Johannes Thumshirn
2017-01-25 10:23 ` Christoph Hellwig [this message]
2017-01-25 10:38 ` Hannes Reinecke
2017-01-25 14:27 ` Ewan D. Milne
2017-01-25 14:38 ` Hannes Reinecke
2017-01-25 15:38 ` James Bottomley
2017-01-25 16:47 ` Hannes Reinecke
2017-01-26 2:45 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170125102329.GA17657@lst.de \
--to=hch@lst.de \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox