From: Christoph Hellwig <hch@infradead.org>
To: John Utz <John.Utz@wdc.com>
Cc: Hannes Reinecke <hare@suse.de>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
James Bottomely <jbottomley@parallels.com>
Subject: Re: [PATCH 4/4] sd: Handle ZBC drives correctly
Date: Tue, 22 Jul 2014 09:19:17 -0700 [thread overview]
Message-ID: <20140722161917.GA763@infradead.org> (raw)
In-Reply-To: <8A51900D08212F40B3DE22453052F69839C47278@wdscexmb02>
Hi John,
I can't really comment much on the ATA side as I'm not overly uptodate
on the ZAC spec.
But a device with the 0x14 device type must have sequential required
zones, which will generate new sense codes when writes outside the
write pointer happens. I'm very concerned about
a) how the SCSI midlayer handles those sense codes
and
b) how we can communicate them to the user of the device, e.g. the
filesystem or user application
Just attaching the device by default without a good solution for these
seems dangerous to me.
next prev parent reply other threads:[~2014-07-22 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 8:27 [PATCHv2 0/4] Initial SMR drive support Hannes Reinecke
2014-07-21 8:27 ` [PATCH 1/4] libata: consolidate ata_dev_classify() Hannes Reinecke
2014-07-21 8:27 ` [PATCH 2/4] libata: Implement ATA_DEV_ZAC Hannes Reinecke
2014-07-21 8:27 ` [PATCH 3/4] libata-scsi: Update SATL for ZAC drives Hannes Reinecke
2014-07-21 8:27 ` [PATCH 4/4] sd: Handle ZBC drives correctly Hannes Reinecke
2014-07-21 11:29 ` Christoph Hellwig
2014-07-21 11:51 ` Hannes Reinecke
2014-07-21 15:01 ` Christoph Hellwig
2014-07-21 16:18 ` John Utz
2014-07-21 16:30 ` John Utz
2014-07-21 17:49 ` Hannes Reinecke
2014-07-22 16:19 ` Christoph Hellwig [this message]
2014-07-22 18:25 ` John Utz
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=20140722161917.GA763@infradead.org \
--to=hch@infradead.org \
--cc=John.Utz@wdc.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).