From: Vasily Averin <vvs@virtuozzo.com>
To: netdev@vger.kernel.org
Cc: linux-nfs@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Subject: [PATCH v3 08/21] nfs client: exit_net cleanup check added
Date: Mon, 6 Nov 2017 16:24:21 +0300 [thread overview]
Message-ID: <f06b08d0-d708-dfa9-5440-a00f59325585@virtuozzo.com> (raw)
In-Reply-To: <4fdc4264-e338-6ee8-a662-7d98b45733a1@virtuozzo.com>
Be sure that nfs_client_list and nfs_volume_list lists initialized
in net_init hook were return to initial state in net_exit hook.
Signed-off-by: Vasily Averin <vvs@virtuozzo.com>
---
fs/nfs/client.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/nfs/client.c b/fs/nfs/client.c
index 22880ef..3966c98 100644
--- a/fs/nfs/client.c
+++ b/fs/nfs/client.c
@@ -204,6 +204,10 @@ void nfs_cleanup_cb_ident_idr(struct net *net)
struct nfs_net *nn = net_generic(net, nfs_net_id);
idr_destroy(&nn->cb_ident_idr);
+ WARN_ONCE(!list_empty(&nn->nfs_client_list),
+ "net %x exit: nfs_client_list is not empty\n", net->ns.inum);
+ WARN_ONCE(!list_empty(&nn->nfs_volume_list),
+ "net %x exit: nfs_volume_list is not empty\n", net->ns.inum);
}
/* nfs_client_lock held */
--
2.7.4
next prev parent reply other threads:[~2017-11-06 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4fdc4264-e338-6ee8-a662-7d98b45733a1@virtuozzo.com>
2017-11-06 13:22 ` [PATCH v3 01/21] grace: replace BUG_ON by WARN_ONCE in exit_net hook Vasily Averin
2017-11-06 20:02 ` J. Bruce Fields
2017-11-09 15:06 ` J. Bruce Fields
2017-11-06 13:23 ` [PATCH v3 02/21] lockd: added cleanup checks " Vasily Averin
2017-11-09 15:06 ` J. Bruce Fields
2017-11-06 13:24 ` [PATCH v3 07/21] nfs4blocklayout: exit_net cleanup check added Vasily Averin
2017-11-06 13:24 ` Vasily Averin [this message]
2017-11-06 13:26 ` [PATCH v3 21/21] sunrpc: " Vasily Averin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f06b08d0-d708-dfa9-5440-a00f59325585@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).