summaryrefslogtreecommitdiff
path: root/drivers/crypto/omap-aes-gcm.c
diff options
context:
space:
mode:
authorDamien Le Moal <damien.lemoal@wdc.com>2020-11-06 20:01:41 +0900
committerJens Axboe <axboe@kernel.dk>2020-11-06 09:36:42 -0700
commite1777d099728a76a8f8090f89649aac961e7e530 (patch)
tree27dac735a263de3ca72c7b8cdbf2c2179fd23f7e /drivers/crypto/omap-aes-gcm.c
parent7ae7a8de054253024624abebd86eb25c5bdaf1c8 (diff)
null_blk: Fix scheduling in atomic with zoned modeblock-5.10-2020-11-07
Commit aa1c09cb65e2 ("null_blk: Fix locking in zoned mode") changed zone locking to using the potentially sleeping wait_on_bit_io() function. This is acceptable when memory backing is enabled as the device queue is in that case marked as blocking, but this triggers a scheduling while in atomic context with memory backing disabled. Fix this by relying solely on the device zone spinlock for zone information protection without temporarily releasing this lock around null_process_cmd() execution in null_zone_write(). This is OK to do since when memory backing is disabled, command processing does not block and the memory backing lock nullb->lock is unused. This solution avoids the overhead of having to mark a zoned null_blk device queue as blocking when memory backing is unused. This patch also adds comments to the zone locking code to explain the unusual locking scheme. Fixes: aa1c09cb65e2 ("null_blk: Fix locking in zoned mode") Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Cc: stable@vger.kernel.org Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/crypto/omap-aes-gcm.c')
0 files changed, 0 insertions, 0 deletions