linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <Anna.Schumaker@Netapp.com>
To: Kirill Tkhai <ktkhai@virtuozzo.com>, <davem@davemloft.net>,
	<trond.myklebust@primarydata.com>, <bfields@fieldses.org>,
	<jlayton@kernel.org>, <dhowells@redhat.com>,
	<keescook@chromium.org>, <dwindsor@gmail.com>,
	<ishkamiel@gmail.com>, <elena.reshetova@intel.com>,
	<linux-nfs@vger.kernel.org>, <linux-afs@lists.infradead.org>,
	<netdev@vger.kernel.org>
Subject: Re: [PATCH net-next nfs 4/6] net: Convert nfs4_dns_resolver_ops
Date: Fri, 23 Mar 2018 14:53:57 -0400	[thread overview]
Message-ID: <32c74ecc-a577-960b-523c-850068e56673@Netapp.com> (raw)
In-Reply-To: <152093818835.8636.5993458301872634002.stgit@localhost.localdomain>



On 03/13/2018 06:49 AM, Kirill Tkhai wrote:
> These pernet_operations look similar to rpcsec_gss_net_ops,
> they just create and destroy another cache. Also they create
> and destroy directory. So, they also look safe to be async.
> 
> Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>

Acked-by: Anna Schumaker <Anna.Schumaker@netapp.com>

> ---
>  fs/nfs/dns_resolve.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/fs/nfs/dns_resolve.c b/fs/nfs/dns_resolve.c
> index 060c658eab66..e90bd69ab653 100644
> --- a/fs/nfs/dns_resolve.c
> +++ b/fs/nfs/dns_resolve.c
> @@ -410,6 +410,7 @@ static void nfs4_dns_net_exit(struct net *net)
>  static struct pernet_operations nfs4_dns_resolver_ops = {
>  	.init = nfs4_dns_net_init,
>  	.exit = nfs4_dns_net_exit,
> +	.async = true,
>  };
>  
>  static int rpc_pipefs_event(struct notifier_block *nb, unsigned long event,
> 

  reply	other threads:[~2018-03-23 18:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 10:49 [PATCH net-next nfs 0/6] Converting pernet_operations (part #7) Kirill Tkhai
2018-03-13 10:49 ` [PATCH net-next nfs 1/6] net: Convert rpcsec_gss_net_ops Kirill Tkhai
2018-03-23 18:53   ` Anna Schumaker
2018-03-26  9:30     ` Kirill Tkhai
2018-03-26 18:36     ` J. Bruce Fields
2018-03-27  8:52       ` Kirill Tkhai
2018-03-23 18:55   ` Anna Schumaker
2018-03-13 10:49 ` [PATCH net-next nfs 2/6] net: Convert sunrpc_net_ops Kirill Tkhai
2018-03-23 18:53   ` Anna Schumaker
2018-03-13 10:49 ` [PATCH net-next nfs 3/6] net: Convert nfsd_net_ops Kirill Tkhai
2018-03-13 10:49 ` [PATCH net-next nfs 4/6] net: Convert nfs4_dns_resolver_ops Kirill Tkhai
2018-03-23 18:53   ` Anna Schumaker [this message]
2018-03-13 10:49 ` [PATCH net-next nfs 5/6] net: Convert nfs4blocklayout_net_ops Kirill Tkhai
2018-03-23 18:54   ` Anna Schumaker
2018-03-13 10:50 ` [PATCH net-next nfs 6/6] net: Convert rxrpc_net_ops Kirill Tkhai
2018-03-13 15:26 ` [PATCH net-next nfs 0/6] Converting pernet_operations (part #7) David Miller
2018-03-15 13:32 ` Kirill Tkhai
2018-03-15 14:24   ` J. Bruce Fields
2018-03-15 14:46     ` Kirill Tkhai
2018-03-20 16:49 ` [PATCH net-next nfs 6/6] net: Convert rxrpc_net_ops David Howells

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=32c74ecc-a577-960b-523c-850068e56673@Netapp.com \
    --to=anna.schumaker@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=dwindsor@gmail.com \
    --cc=elena.reshetova@intel.com \
    --cc=ishkamiel@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=keescook@chromium.org \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=netdev@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 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).