From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, devel@openvz.org,
linux-kernel@vger.kernel.org, jlayton@redhat.com
Subject: [PATCH v2 0/4] SUNRPC: PipeFS races fixes
Date: Tue, 11 Jun 2013 18:39:02 +0400 [thread overview]
Message-ID: <20130611143725.16046.17279.stgit@localhost.localdomain> (raw)
This series fixes races between PipeFS mount/umount notification calls and
SUNRPC clients creation and destruction.
https://bugzilla.redhat.com/show_bug.cgi?id=924649
v2: Fixed few silly locking bugs.
The following series implements...
---
Stanislav Kinsbursky (4):
SUNRPC: split client creation routine into setup and registration
SUNRPC: fix races on PipeFS MOUNT notifications
SUNRPC: fix races on PipeFS UMOUNT notifications
SUNRPC: PipeFS MOUNT notification optimization for dying clients
net/sunrpc/clnt.c | 71 ++++++++++++++++++++++++++++++-------------------
net/sunrpc/rpc_pipe.c | 5 +++
2 files changed, 48 insertions(+), 28 deletions(-)
next reply other threads:[~2013-06-11 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 14:39 Stanislav Kinsbursky [this message]
2013-06-11 14:39 ` [PATCH v2 1/4] SUNRPC: split client creation routine into setup and registration Stanislav Kinsbursky
2013-06-11 14:39 ` [PATCH v2 2/4] SUNRPC: fix races on PipeFS MOUNT notifications Stanislav Kinsbursky
2013-06-17 18:20 ` Myklebust, Trond
2013-06-18 6:41 ` Stanislav Kinsbursky
2013-06-11 14:39 ` [PATCH v2 3/4] SUNRPC: fix races on PipeFS UMOUNT notifications Stanislav Kinsbursky
2013-06-11 14:39 ` [PATCH v2 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=20130611143725.16046.17279.stgit@localhost.localdomain \
--to=skinsbursky@parallels.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 \
/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).