From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@openvz.org" <devel@openvz.org>
Subject: Re: [PATCH 0/3] SUNRPC: three bugfixes for PipeFS event handling
Date: Thu, 26 Apr 2012 00:59:07 +0400 [thread overview]
Message-ID: <4F98659B.6060409@parallels.com> (raw)
In-Reply-To: <20120425182409.GE751@fieldses.org>
25.04.2012 22:24, J. Bruce Fields написал:
> On Fri, Apr 20, 2012 at 06:18:59PM +0400, Stanislav Kinsbursky wrote:
>> These bugfixes were caught (or noticed) due to the following simple script:
> I'm assuming Trond should take these (possibly for 3.4?).
I think so.
But would be great if you'll take them as well (since I'm mostly working
with your tree).
Of course, only if its not a big deal for you.
But if there will be any conflicts - then don't worry. I can just keep
these patches in my repo.
> --b.
>
>> ======================================================================
>>
>> #!/bin/bash
>> service rpcbind stop
>> service rpcidmapd stop
>> killall -TERM rpc.statd
>> umount /var/lib/nfs/rpc_pipefs
>> rmmod nfs
>> service rpcbind start
>> service nfs start
>> mount -t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs
>>
>> =======================================================================
>>
>> The following series consists of:
>>
>> ---
>>
>> Stanislav Kinsbursky (3):
>> SUNRPC: skip clients with program without PipeFS entries
>> SUNRPC: traverse clients tree on PipeFS event
>> SUNRPC: set per-net PipeFS superblock before notification
>>
>>
>> net/sunrpc/clnt.c | 34 ++++++++++++++++++++++++++++------
>> net/sunrpc/rpc_pipe.c | 3 ++-
>> 2 files changed, 30 insertions(+), 7 deletions(-)
>>
next prev parent reply other threads:[~2012-04-25 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 14:18 [PATCH 0/3] SUNRPC: three bugfixes for PipeFS event handling Stanislav Kinsbursky
2012-04-20 14:19 ` [PATCH 1/3] SUNRPC: skip clients with program without PipeFS entries Stanislav Kinsbursky
2012-04-20 14:19 ` [PATCH 2/3] SUNRPC: traverse clients tree on PipeFS event Stanislav Kinsbursky
2012-04-26 18:11 ` Myklebust, Trond
2012-04-26 18:11 ` Myklebust, Trond
2012-04-26 18:26 ` Stanislav Kinsbursky
2012-04-27 9:00 ` [PATCH v2 " Stanislav Kinsbursky
2012-04-20 14:19 ` [PATCH 3/3] SUNRPC: set per-net PipeFS superblock before notification Stanislav Kinsbursky
2012-04-25 18:24 ` [PATCH 0/3] SUNRPC: three bugfixes for PipeFS event handling J. Bruce Fields
2012-04-25 20:59 ` Stanislav Kinsbursky [this message]
2012-04-25 21:02 ` J. Bruce Fields
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=4F98659B.6060409@parallels.com \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=devel@openvz.org \
--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.