On 29/05/2024 06:04, 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 freezer 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<h...@lst.de>
It would be nice to improve this eventually (to use the atomic queue
limits API). Anyway:
Reviewed-by: John Garry <john.g.ga...@oracle.com>
