On 5/29/24 14: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 s/freezer/freeze > 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> With the typo fixed, looks OK to me. Reviewed-by: Damien Le Moal <dlemoal@xxxxxxxxxx> -- Damien Le Moal Western Digital Research
