From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: linux-ide@vger.kernel.org,
"Maciej S . Szmigiero" <mail@maciej.szmigiero.name>
Cc: Hannes Reinecke <hare@suse.de>
Subject: [PATCH v3 4/6] ata: libata: Fix FUA handling in ata_build_rw_tf()
Date: Thu, 27 Oct 2022 16:50:24 +0900 [thread overview]
Message-ID: <20221027075026.240017-5-damien.lemoal@opensource.wdc.com> (raw)
In-Reply-To: <20221027075026.240017-1-damien.lemoal@opensource.wdc.com>
If a user issues a write command with the FUA bit set for a device with
NCQ support disabled (that is, the device queue depth was set to 1), the
LBA 48 command WRITE DMA FUA EXT must be used. However,
ata_build_rw_tf() ignores this and first test if LBA 28 can be used.
That is, for small FUA writes at low LBAs, ata_rwcmd_protocol() will
cause the write to fail.
Fix this by preventing the use of LBA 28 for any FUA write request.
While at it, also early test if the request is a FUA read and fail these
requests for the NCQ-disabled case instead of relying on
ata_rwcmd_protocol() returning an error.
Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
---
drivers/ata/libata-core.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 81b20ffb1554..fea06f41f371 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -725,9 +725,21 @@ int ata_build_rw_tf(struct ata_queued_cmd *qc, u64 block, u32 n_block,
class == IOPRIO_CLASS_RT)
tf->hob_nsect |= ATA_PRIO_HIGH << ATA_SHIFT_PRIO;
} else if (dev->flags & ATA_DFLAG_LBA) {
+ bool lba28_ok;
+
+ if (tf->flags & ATA_TFLAG_FUA) {
+ /* FUA reads are not defined */
+ if (!(tf->flags & ATA_TFLAG_WRITE))
+ return -EINVAL;
+ /* We need LBA48 / WRITE DMA FUA EXT for FUA writes */
+ lba28_ok = false;
+ } else {
+ lba28_ok = lba_28_ok(block, n_block);
+ }
+
tf->flags |= ATA_TFLAG_LBA;
- if (lba_28_ok(block, n_block)) {
+ if (lba28_ok) {
/* use LBA28 */
tf->device |= (block >> 24) & 0xf;
} else if (lba_48_ok(block, n_block)) {
@@ -742,9 +754,10 @@ int ata_build_rw_tf(struct ata_queued_cmd *qc, u64 block, u32 n_block,
tf->hob_lbah = (block >> 40) & 0xff;
tf->hob_lbam = (block >> 32) & 0xff;
tf->hob_lbal = (block >> 24) & 0xff;
- } else
+ } else {
/* request too large even for LBA48 */
return -ERANGE;
+ }
if (unlikely(!ata_set_rwcmd_protocol(dev, tf)))
return -EINVAL;
--
2.37.3
next prev parent reply other threads:[~2022-10-27 7:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 7:50 [PATCH v3 0/6] Improve libata support for FUA Damien Le Moal
2022-10-27 7:50 ` [PATCH v3 1/6] ata: libata: Introduce ata_ncq_supported() Damien Le Moal
2022-10-27 9:24 ` Hannes Reinecke
2022-10-27 7:50 ` [PATCH v3 2/6] ata: libata: Rename and cleanup ata_rwcmd_protocol() Damien Le Moal
2022-10-27 9:25 ` Hannes Reinecke
2022-10-27 9:43 ` Sergei Shtylyov
2022-10-27 7:50 ` [PATCH v3 3/6] ata: libata: cleanup fua handling Damien Le Moal
2022-10-27 9:32 ` Hannes Reinecke
2022-10-27 7:50 ` Damien Le Moal [this message]
2022-10-27 8:21 ` [PATCH v3 4/6] ata: libata: Fix FUA handling in ata_build_rw_tf() Niklas Cassel
2022-10-27 9:12 ` Damien Le Moal
2022-10-27 9:42 ` Hannes Reinecke
2022-10-27 22:22 ` Damien Le Moal
2022-10-28 10:01 ` Hannes Reinecke
2022-10-28 16:45 ` Maciej S. Szmigiero
2022-10-28 16:45 ` Maciej S. Szmigiero
2022-10-27 7:50 ` [PATCH v3 5/6] ata: libata: blacklist FUA support for known buggy drives Damien Le Moal
2022-10-27 7:50 ` [PATCH v3 6/6] ata: libata: Enable fua support by default Damien Le Moal
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=20221027075026.240017-5-damien.lemoal@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=hare@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
/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