From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Jeff Layton <jlayton@poochiereds.net>,
<linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<skinsbursky@virtuozzo.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH] lockd: create NSM handles per net namespace
Date: Fri, 2 Oct 2015 12:16:38 +0300 [thread overview]
Message-ID: <560E4B76.40504@virtuozzo.com> (raw)
In-Reply-To: <20151001182630.GC10316@fieldses.org>
On 10/01/2015 09:26 PM, J. Bruce Fields wrote:
> On Thu, Oct 01, 2015 at 07:36:19PM +0300, Andrey Ryabinin wrote:
>> On 09/29/2015 09:47 PM, J. Bruce Fields wrote:
>>> On Wed, Sep 23, 2015 at 03:49:29PM +0300, Andrey Ryabinin wrote:
>>>> Commit cb7323fffa85 ("lockd: create and use per-net NSM
>>>> RPC clients on MON/UNMON requests") introduced per-net
>>>> NSM RPC clients. Unfortunately this doesn't make any sense
>>>> without per-net nsm_handle.
>>>
>>> Makes sense to me. Is anyone doing testing to make sure we've got this
>>> right now?
>>>
>>> (For example, have you reproduced the below problem and verified that
>>> it's fixed after this patch?)
>>>
>>
>> Yes, that NULL-ptr was actually hit, so I've fixed it with this patch.
>
> Great, thanks. I'm queuing this up for 4.4 in the nfsd tree (assuming
> that's OK with Trond).
>
> How extensively have you tested containerized nfs (client or server
> side) at this point?
We have some tests for that, but we don't run them on upstream kernels,
only on OpenVZ.
> Have you seen any other issues?
>
None, so far.
prev parent reply other threads:[~2015-10-02 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 12:49 [PATCH] lockd: create NSM handles per net namespace Andrey Ryabinin
2015-09-29 18:47 ` J. Bruce Fields
2015-10-01 16:36 ` Andrey Ryabinin
2015-10-01 18:26 ` J. Bruce Fields
2015-10-02 9:16 ` Andrey Ryabinin [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=560E4B76.40504@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@virtuozzo.com \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 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.