Re: [PATCH 2/2] ata: libata-core: Set capacity to zero for a security locked drive

[Damien Le Moal <dlemoal@kernel.org>]

On 11/19/25 11:13 PM, Niklas Cassel wrote:
> For Security locked drives (drives that have Security enabled, and have
> not been Security unlocked by boot firmware), the automatic partition
> scanning will result in the user being spammed with errors such as:
> 
>   ata5.00: failed command: READ DMA
>   ata5.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 7 dma 4096 in
>            res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
>   ata5.00: status: { DRDY ERR }
>   ata5.00: error: { ABRT }
>   sd 4:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
>   sd 4:0:0:0: [sda] tag#7 Sense Key : Aborted Command [current]
>   sd 4:0:0:0: [sda] tag#7 Add. Sense: No additional sense information
> 
> during boot, because most commands except for IDENTIFY will be aborted by
> a Security locked drive.
> 
> For a Security locked drive, set capacity to zero, so that no automatic
> partition scanning will happen.
> 
> If the user later unlocks the drive using e.g. hdparm, the close() by the
> user space application should trigger a revalidation of the drive.
> 
> Signed-off-by: Niklas Cassel <cassel@kernel.org>

Looks good.

Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

-- 
Damien Le Moal
Western Digital Research