All of lore.kernel.org
 help / color / mirror / Atom feed
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: Re: [PATCH 0/3] SUNRPC: PipeFS races fixes
Date: Mon, 10 Jun 2013 18:41:34 +0400	[thread overview]
Message-ID: <51B5E59E.1000501@parallels.com> (raw)
In-Reply-To: <20130610143725.7498.72391.stgit@localhost.localdomain>

This series has flaws. Will fix and resend.
Sorry for noise.

10.06.2013 18:39, Stanislav Kinsbursky пишет:
> This series fixed races between PipeFS mount/umount notification calls and
> SUNRPC clients creation and destruction.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=924649
>
> The following series implements...
>
> ---
>
> Stanislav Kinsbursky (3):
>        SUNRPC: fix races on PipeFS UMOUNT notifications
>        SUNRPC: fix races on PipeFS UMOUNT notifications
>        SUNRPC: PipeFS MOUNT notification optimization for dying clients
>
>
>   net/sunrpc/clnt.c     |   14 +++++++++-----
>   net/sunrpc/rpc_pipe.c |    5 ++++-
>   2 files changed, 13 insertions(+), 6 deletions(-)
>


-- 
Best regards,
Stanislav Kinsbursky

      parent reply	other threads:[~2013-06-10 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 14:39 [PATCH 0/3] SUNRPC: PipeFS races fixes Stanislav Kinsbursky
2013-06-10 14:40 ` [PATCH 1/3] SUNRPC: fix races on PipeFS UMOUNT notifications Stanislav Kinsbursky
2013-06-10 14:40 ` [PATCH 2/3] " Stanislav Kinsbursky
2013-06-10 14:40 ` [PATCH 3/3] SUNRPC: PipeFS MOUNT notification optimization for dying clients Stanislav Kinsbursky
2013-06-10 14:41 ` Stanislav Kinsbursky [this message]

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=51B5E59E.1000501@parallels.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.