From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org, xxjack12xx@gmail.com,
Niklas Cassel <cassel@kernel.org>
Subject: [PATCH 0/3] ata: libata: Quirk DELLBOSS VD MV.R00-0 max_sectors
Date: Mon, 24 Nov 2025 14:44:15 +0100 [thread overview]
Message-ID: <20251124134414.3057512-5-cassel@kernel.org> (raw)
Hello there,
a recent change:
9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP")
bumped the default max_sectors_kb from 1280 to 4096.
It seems like a lot for SATA controllers are buggy and don't really like
this, see:
https://bugzilla.kernel.org/show_bug.cgi?id=220693
For now, we only add a DELLBOSS VD MV.R00-0 max_sectors quirk, but surely
more quirks are coming, so change libata-core to allow for more quirks,
since after this change, all quirks bits are used.
Niklas Cassel (3):
ata: libata: Move quirk flags to their own enum
ata: libata-core: Quirk DELLBOSS VD MV.R00-0 max_sectors
ata: libata: Allow more quirks
drivers/ata/libata-core.c | 16 +++++++-
include/linux/ata.h | 1 +
include/linux/libata.h | 81 +++++++++++++++++++++------------------
3 files changed, 58 insertions(+), 40 deletions(-)
--
2.52.0
next reply other threads:[~2025-11-24 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 13:44 Niklas Cassel [this message]
2025-11-24 13:44 ` [PATCH 1/3] ata: libata: Move quirk flags to their own enum Niklas Cassel
2025-11-25 4:29 ` Damien Le Moal
2025-11-24 13:44 ` [PATCH 2/3] ata: libata-core: Quirk DELLBOSS VD MV.R00-0 max_sectors Niklas Cassel
2025-11-24 14:09 ` Niklas Cassel
2025-11-24 20:51 ` Jack L.
2025-11-25 0:00 ` Jack L.
2025-11-25 0:20 ` Damien Le Moal
2025-11-24 13:44 ` [PATCH 3/3] ata: libata: Allow more quirks Niklas Cassel
2025-11-25 4:30 ` 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=20251124134414.3057512-5-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=xxjack12xx@gmail.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 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.