From: Niklas Cassel <cassel@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-ide@vger.kernel.org
Cc: Damien Le Moal <dlemoal@kernel.org>, Niklas Cassel <cassel@kernel.org>
Subject: [GIT PULL] ata fixes for 6.18-rc7
Date: Fri, 21 Nov 2025 16:11:04 +0100 [thread overview]
Message-ID: <20251121151104.2645094-1-cassel@kernel.org> (raw)
Linus,
The following changes since commit 12d724f2852d094d68dccaf5101e0ef89a971cde:
ata: libata-core: relax checks in ata_read_log_directory() (2025-10-13 09:12:36 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux tags/ata-6.18-rc7
for you to fetch changes up to 91842ed844a068a41a38f97a1ac5535b909279cd:
ata: libata-core: Set capacity to zero for a security locked drive (2025-11-20 13:37:18 +0100)
----------------------------------------------------------------
ata fixes for 6.18-rc7
- Add a missing refcount decrement in ata_scsi_dev_rescan() when
the device or its queue is not running. In the case where the
device is running, the recount is already decremented properly
(Yihang Li)
- Generate the proper sense code for a Security locked device.
There was a regression caused by a recent change of how sense
data is generated for commands that did not provide any sense
data. This broke system suspend for Security locked devices.
Generate the sense data that the SCSI disk driver expects for
a Security locked device so that system supend works again
(me)
- Set capacity to zero for a Security locked device.
All I/O commands will be aborted by a Security locked device.
Thus, the block layer disk partition scanning will result in
a bunch of, for the user, confusing I/O errors in dmesg during
boot. Since a Security locked device is unusable anyway, set
the capacity to zero, to avoid the disk partition scanning
during boot. We still create the block device in /dev such
that the user may unlock the device using e.g. hdparm (me)
----------------------------------------------------------------
Niklas Cassel (2):
ata: libata-scsi: Fix system suspend for a security locked drive
ata: libata-core: Set capacity to zero for a security locked drive
Yihang Li (1):
ata: libata-scsi: Add missing scsi_device_put() in ata_scsi_dev_rescan()
drivers/ata/libata-core.c | 10 ++++++++++
drivers/ata/libata-scsi.c | 11 ++++++++++-
include/linux/ata.h | 1 +
3 files changed, 21 insertions(+), 1 deletion(-)
next reply other threads:[~2025-11-21 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 15:11 Niklas Cassel [this message]
2025-11-21 19:19 ` [GIT PULL] ata fixes for 6.18-rc7 pr-tracker-bot
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=20251121151104.2645094-1-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=torvalds@linux-foundation.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