diff options
author | Christophe JAILLET <christophe.jaillet@wanadoo.fr> | 2022-02-15 09:32:34 +0300 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2022-02-28 05:21:21 +0300 |
commit | e3af2e3b0019d9040f7cce39a8992cb4c03a087b (patch) | |
tree | fdedca855bae79bd71aef36b1f5241d73bce7abf /Documentation/scsi | |
parent | c5b483d5c1a26b6006180f5dc7b2f8674f19afa3 (diff) | |
download | linux-e3af2e3b0019d9040f7cce39a8992cb4c03a087b.tar.xz |
scsi: message: fusion: Use GFP_KERNEL instead of GFP_ATOMIC in non-atomic context
Just a few lines below this kzalloc() we have a mutex_lock() which can
sleep.
Moreover, the only way to call this function is when a delayed work is
schedule. And delayed work can sleep:
INIT_DELAYED_WORK(&fw_event->work, mptsas_firmware_event_work);
--> mptsas_firmware_event_work()
--> mptsas_send_link_status_event()
--> mptsas_expander_add()
So there is really no good reason to use GFP_ATOMIC here. Change it to
GFP_KERNEL to give more opportunities to the kernel.
Link: https://lore.kernel.org/r/eccb2179ce800529851ed4fabc9d3f95fbbf7d7f.1644906731.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'Documentation/scsi')
0 files changed, 0 insertions, 0 deletions