From: Vasily Averin <vvs@virtuozzo.com>
To: Jeff Layton <jlayton@redhat.com>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Scott Mayhew <smayhew@redhat.com>
Subject: Re: [PATCH 1/2] NFSD: notifiers registration cleanup
Date: Thu, 22 Sep 2016 11:35:31 +0300 [thread overview]
Message-ID: <84473086-ba97-64c9-ae4d-40bbe82eeef6@virtuozzo.com> (raw)
In-Reply-To: <1474464010.32518.3.camel@redhat.com>
On 21.09.2016 16:20, Jeff Layton wrote:
> Good catch. I'm not very fond of the refcounting this here but it
> should
> serve the purpose and I don't have anything better to suggest. FWIW, I
> think the nfsd_mutex is held during all of these operations so we
> probably don't need atomics for the refcount.
I've copied idea from netfilters,
look at using of masquerade_notifier_refcount
Perhaps someday in future we'll replace all such cases by some common primitive.
next prev parent reply other threads:[~2016-09-22 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 12:33 Vasily Averin
2016-09-21 13:20 ` Jeff Layton
2016-09-22 8:35 ` Vasily Averin [this message]
2016-09-22 16:15 ` 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=84473086-ba97-64c9-ae4d-40bbe82eeef6@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.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
all inboxes | Powered by JetHome®