NFS: Use an appropriate work queue for direct-write completion
authorNeilBrown <neilb@suse.com>
Tue, 7 Aug 2018 23:20:02 +0000 (09:20 +1000)
committerAnna Schumaker <Anna.Schumaker@Netapp.com>
Wed, 8 Aug 2018 21:07:38 +0000 (17:07 -0400)
commit46483c2ea4664679130d6489112f180c2bfc801d
tree4417e26e7713b54f319b4ce6f8712c99d07d7cd5
parent72bf75cfc00c02aa66ef6133048f37aa5d88825c
NFS: Use an appropriate work queue for direct-write completion

When a direct-write completes, a work_struct is schedule to handle
the completion.
When NFS is being used for swap, the direct write might be a swap-out,
so memory allocation can block until the write completes.
The work queue currently used is not WQ_MEM_RECLAIM, so tasks
can block waiting for memory - this leads to deadlock.

So use nfsiod_workqueue instead.  This will always have a running
thread, and work items should never block waiting for memory.

Signed-off-by: Neil Brown <neilb@suse.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
fs/nfs/direct.c