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 0/6] Improve libata support for FUA
Date: Thu, 27 Oct 2022 16:50:20 +0900 [thread overview]
Message-ID: <20221027075026.240017-1-damien.lemoal@opensource.wdc.com> (raw)
These patches cleanup and improve libata support for the FUA device
feature. Patch 6 enables FUA support by default for any drive that
reports supporting the feature as well as NCQ.
Changes from v2:
- Added patch 1 and 2 as preparatory patches
- Added patch 4 to fix FUA writes handling for the non-ncq case. Note
that it is possible that the drives blacklisted in patch 5 are
actually OK since the code back in 2012 had the issue with the wrong
use of LBA 28 commands for FUA writes.
Changes from v1:
- Removed Maciej's patch 2. Instead, blacklist drives which are known
to have a buggy FUA support.
Damien Le Moal (6):
ata: libata: Introduce ata_ncq_supported()
ata: libata: Rename and cleanup ata_rwcmd_protocol()
ata: libata: cleanup fua handling
ata: libata: Fix FUA handling in ata_build_rw_tf()
ata: libata: blacklist FUA support for known buggy drives
ata: libata: Enable fua support by default
.../admin-guide/kernel-parameters.txt | 3 +
drivers/ata/libata-core.c | 80 +++++++++++++++----
drivers/ata/libata-scsi.c | 30 +------
include/linux/libata.h | 34 +++++---
4 files changed, 93 insertions(+), 54 deletions(-)
--
2.37.3
next 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 Damien Le Moal [this message]
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 ` [PATCH v3 4/6] ata: libata: Fix FUA handling in ata_build_rw_tf() Damien Le Moal
2022-10-27 8:21 ` 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-1-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.