diff options
| author |   Jack Wang <jinpu.wang@cloud.ionos.com> | 2020-07-24 16:45:08 +0530 |
|---|---|---|
| committer |   Jason Gunthorpe <jgg@nvidia.com> | 2020-07-29 14:26:53 -0300 |
| commit | 03ed5a8cda659e3c71d106b0dd4ce6520e4dcd6e (patch) | |
| tree | 0c0607bb3a3cf48c21efee54a45fe97ae0c2ce99 /include/rdma/uverbs_ioctl.h | |
| parent | RDMA/rtrs-clt: add an additional random 8 seconds before reconnecting (diff) | |
| download | linux-dev-03ed5a8cda659e3c71d106b0dd4ce6520e4dcd6e.tar.xz linux-dev-03ed5a8cda659e3c71d106b0dd4ce6520e4dcd6e.zip | |
RDMA/rtrs: remove WQ_MEM_RECLAIM for rtrs_wq
lockdep triggers a warning from time to time when running a regression
test:
rnbd_client L685: </dev/nullb0@bla> Device disconnected.
rnbd_client L1756: Unloading module
workqueue: WQ_MEM_RECLAIM rtrs_client_wq:rtrs_clt_reconnect_work [rtrs_client] is flushing !WQ_MEM_RECLAIM ib_addr:process_one_req [ib_core]
WARNING: CPU: 2 PID: 18824 at kernel/workqueue.c:2517 check_flush_dependency+0xad/0x130
The root cause is workqueue core expect flushing should not be done for a
!WQ_MEM_RECLAIM wq from a WQ_MEM_RECLAIM workqueue.
In above case ib_addr workqueue without WQ_MEM_RECLAIM, but rtrs_wq
WQ_MEM_RECLAIM.
To avoid the warning, remove the WQ_MEM_RECLAIM flag.
Fixes: 9cb837480424 ("RDMA/rtrs: server: main functionality")
Fixes: 6a98d71daea1 ("RDMA/rtrs: client: main functionality")
Link: https://lore.kernel.org/r/20200724111508.15734-4-haris.iqbal@cloud.ionos.com
Signed-off-by: Jack Wang <jinpu.wang@cloud.ionos.com>
Signed-off-by: Md Haris Iqbal <haris.iqbal@cloud.ionos.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'include/rdma/uverbs_ioctl.h')
0 files changed, 0 insertions, 0 deletions