From: William Dauchy <wdauchy@gmail.com>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
Linux NFS mailing list <linux-nfs@vger.kernel.org>,
devel@openvz.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jlayton@redhat.com
Subject: Re: [PATCH v4] SUNRPC: fix races on PipeFS UMOUNT notifications
Date: Fri, 28 Jun 2013 13:51:23 +0200 [thread overview]
Message-ID: <CAJ75kXaRTfkCvT+=PdmHaRAXGKuMYW7aRRpGQJrQkfi6nDO9DQ@mail.gmail.com> (raw)
In-Reply-To: <20130626061448.32202.192.stgit@localhost.localdomain>
On Wed, Jun 26, 2013 at 8:15 AM, Stanislav Kinsbursky
<skinsbursky@parallels.com> wrote:
> diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> index b827a4b..41f180c 100644
> --- a/net/sunrpc/clnt.c
> +++ b/net/sunrpc/clnt.c
> @@ -236,8 +236,6 @@ static struct rpc_clnt *rpc_get_client_for_event(struct net *net, int event)
> continue;
> if (rpc_clnt_skip_event(clnt, event))
> continue;
> - if (atomic_inc_not_zero(&clnt->cl_count) == 0)
> - continue;
> spin_unlock(&sn->rpc_client_lock);
> return clnt;
> }
> @@ -254,7 +252,6 @@ static int rpc_pipefs_event(struct notifier_block *nb, unsigned long event,
>
> while ((clnt = rpc_get_client_for_event(sb->s_fs_info, event))) {
> error = __rpc_pipefs_event(clnt, event, sb);
> - rpc_release_client(clnt);
> if (error)
> break;
> }
> @@ -641,8 +638,8 @@ rpc_free_client(struct rpc_clnt *clnt)
> rcu_dereference(clnt->cl_xprt)->servername);
> if (clnt->cl_parent != clnt)
> rpc_release_client(clnt->cl_parent);
> - rpc_unregister_client(clnt);
> rpc_clnt_remove_pipedir(clnt);
> + rpc_unregister_client(clnt);
> rpc_free_iostats(clnt->cl_metrics);
> kfree(clnt->cl_principal);
> clnt->cl_metrics = NULL;
> diff --git a/net/sunrpc/rpc_pipe.c b/net/sunrpc/rpc_pipe.c
> index c512448..9b4ec5b 100644
> --- a/net/sunrpc/rpc_pipe.c
> +++ b/net/sunrpc/rpc_pipe.c
> @@ -1165,12 +1165,12 @@ static void rpc_kill_sb(struct super_block *sb)
> goto out;
> }
> sn->pipefs_sb = NULL;
> - mutex_unlock(&sn->pipefs_sb_lock);
> dprintk("RPC: sending pipefs UMOUNT notification for net %p%s\n",
> net, NET_NAME(net));
> blocking_notifier_call_chain(&rpc_pipefs_notifier_list,
> RPC_PIPEFS_UMOUNT,
> sb);
> + mutex_unlock(&sn->pipefs_sb_lock);
> put_net(net);
> out:
> kill_litter_super(sb);
are these patches validated?
any chance to see them in tree soon? I wasn't able to find them on
http://git.linux-nfs.org/?p=trondmy/linux-nfs.git
Thanks,
--
William
next prev parent reply other threads:[~2013-06-28 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 7:52 [PATCH v3 0/4] SUNRPC: PipeFS races fixes Stanislav Kinsbursky
2013-06-24 7:52 ` [PATCH v3 1/4] SUNRPC: fix races on PipeFS MOUNT notifications Stanislav Kinsbursky
2013-06-24 7:52 ` [PATCH v3 2/4] SUNRPC: fix races on PipeFS UMOUNT notifications Stanislav Kinsbursky
2013-06-25 16:13 ` Myklebust, Trond
2013-06-26 5:32 ` Stanislav Kinsbursky
2013-06-26 6:15 ` [PATCH v4] " Stanislav Kinsbursky
2013-06-28 11:51 ` William Dauchy [this message]
2013-06-24 7:52 ` [PATCH v3 3/4] SUNRPC: split client creation routine into setup and registration Stanislav Kinsbursky
2013-06-24 7:52 ` [PATCH v3 4/4] SUNRPC: PipeFS MOUNT notification optimization for dying clients Stanislav Kinsbursky
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='CAJ75kXaRTfkCvT+=PdmHaRAXGKuMYW7aRRpGQJrQkfi6nDO9DQ@mail.gmail.com' \
--to=wdauchy@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=devel@openvz.org \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@parallels.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).