[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1509897719.5851.2.camel@primarydata.com>
Date: Sun, 5 Nov 2017 16:02:01 +0000
From: Trond Myklebust <trondmy@...marydata.com>
To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"vvs@...tuozzo.com" <vvs@...tuozzo.com>
CC: "anna.schumaker@...app.com" <anna.schumaker@...app.com>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>
Subject: Re: [PATCH 06/21] nfs client: exit_net cleanup check added
On Sun, 2017-11-05 at 13:00 +0300, Vasily Averin wrote:
> 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@...tuozzo.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..7c0691c 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(!list_empty(&nn->nfs_client_list),
> + "net %p exit: nfs_client_list is not empty\n", net);
> + WARN(!list_empty(&nn->nfs_volume_list),
> + "net %p exit: nfs_volume_list is not empty\n", net);
> }
>
Why do we need these? Is there a specific bug that you are trying to
track down?
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@...marydata.com
Powered by blists - more mailing lists