The patch titled
svcrdma: add flush_scheduled_work to module exit function
has been added to the -mm tree. Its filename is
svcrdma-add-flush_scheduled_work-to-module-exit-function.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: svcrdma: add flush_scheduled_work to module exit function
From: Tom Tucker <tom@xxxxxxxxxxxxxxxxxxxxx>
Make certain all transports pending free are flushed from the wq
before unloading the module.
Signed-off-by: Tom Tucker <tom@xxxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
net/sunrpc/xprtrdma/svc_rdma.c | 1 +
1 file changed, 1 insertion(+)
diff -puN net/sunrpc/xprtrdma/svc_rdma.c~svcrdma-add-flush_scheduled_work-to-module-exit-function net/sunrpc/xprtrdma/svc_rdma.c
--- a/net/sunrpc/xprtrdma/svc_rdma.c~svcrdma-add-flush_scheduled_work-to-module-exit-function
+++ a/net/sunrpc/xprtrdma/svc_rdma.c
@@ -236,6 +236,7 @@ static ctl_table svcrdma_root_table[] =
void svc_rdma_cleanup(void)
{
dprintk("SVCRDMA Module Removed, deregister RPC RDMA transport\n");
+ flush_scheduled_work();
if (svcrdma_table_header) {
unregister_sysctl_table(svcrdma_table_header);
svcrdma_table_header = NULL;
_
Patches currently in -mm which might be from tom@xxxxxxxxxxxxxxxxxxxxx are
linux-next.patch
svcrdma-fix-compile-warning-on-32-bit-platforms.patch
svcrdma-fix-compile-warning-on-32-bit-platforms-checkpatch-fixes.patch
svcrdma-add-flush_scheduled_work-to-module-exit-function.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
