| Message ID | 20220218180515.27455-1-sreekanth.reddy@broadcom.com |
|---|---|
| State | New |
| Headers | show |
| Series | mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning | expand |
Sreekanth, > Fix below warning by not allocating driver's event handling worker > queue with WQ_MEM_RECLAIM flag enabled. Applied to 5.18/scsi-staging, thanks!
On Fri, 18 Feb 2022 23:35:15 +0530, Sreekanth Reddy wrote: > Fix below warning by not allocating driver's event handling > worker queue with WQ_MEM_RECLAIM flag enabled. > > workqueue: WQ_MEM_RECLAIM > mpi3mr_fwevt_worker [mpi3mr] is flushing !WQ_MEM_RECLAIM events > > > [...] Applied to 5.18/scsi-queue, thanks! [1/1] mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning https://git.kernel.org/mkp/scsi/c/334ae6459aa3
diff --git a/drivers/scsi/mpi3mr/mpi3mr_os.c b/drivers/scsi/mpi3mr/mpi3mr_os.c index 68f874b38de8..f7cd70a15ea6 100644 --- a/drivers/scsi/mpi3mr/mpi3mr_os.c +++ b/drivers/scsi/mpi3mr/mpi3mr_os.c @@ -4308,7 +4308,7 @@ mpi3mr_probe(struct pci_dev *pdev, const struct pci_device_id *id) snprintf(mrioc->fwevt_worker_name, sizeof(mrioc->fwevt_worker_name), "%s%d_fwevt_wrkr", mrioc->driver_name, mrioc->id); mrioc->fwevt_worker_thread = alloc_ordered_workqueue( - mrioc->fwevt_worker_name, WQ_MEM_RECLAIM); + mrioc->fwevt_worker_name, 0); if (!mrioc->fwevt_worker_thread) { ioc_err(mrioc, "failure at %s:%d/%s()!\n", __FILE__, __LINE__, __func__);
Fix below warning by not allocating driver's event handling worker queue with WQ_MEM_RECLAIM flag enabled. workqueue: WQ_MEM_RECLAIM mpi3mr_fwevt_worker [mpi3mr] is flushing !WQ_MEM_RECLAIM events Signed-off-by: Sreekanth Reddy <sreekanth.reddy@broadcom.com> --- drivers/scsi/mpi3mr/mpi3mr_os.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)