On 31/05/24 09:48AM, Christoph Hellwig wrote:
A few drivers optimistically try to support discard, write zeroes and secure erase and disable the features from the I/O completion handler if the hardware can't support them. This disable can't be done using the atomic queue limits API because the I/O completion handlers can't take sleeping locks or freeze the queue. Keep the existing clearing of the relevant field to zero, but replace the old blk_queue_max_* APIs with new disable APIs that force the value to 0. Signed-off-by: Christoph Hellwig <hch@xxxxxx> Reviewed-by: Bart Van Assche <bvanassche@xxxxxxx> Reviewed-by: Damien Le Moal <dlemoal@xxxxxxxxxx> ---
Reviewed-by: Nitesh Shetty <nj.shetty@xxxxxxxxxxx>
