From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: davem@davemloft.net, anna.schumaker@netapp.com,
trond.myklebust@primarydata.com, ktkhai@virtuozzo.com,
netdev@vger.kernel.org
Subject: [PATCH net-next v1 3/4] net: Convert nfs4_dns_resolver_ops
Date: Mon, 26 Mar 2018 12:29:04 +0300 [thread overview]
Message-ID: <152205654436.6058.5257383048557457339.stgit@localhost.localdomain> (raw)
In-Reply-To: <152205594525.6058.12471686205983419325.stgit@localhost.localdomain>
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,
next prev parent reply other threads:[~2018-03-26 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 9:28 [PATCH net-next v1 0/4] Converting pernet_operations (part #7.1) Kirill Tkhai
2018-03-26 9:28 ` [PATCH net-next v1 1/4] net: Convert rpcsec_gss_net_ops Kirill Tkhai
2018-03-26 9:28 ` [PATCH net-next v1 2/4] net: Convert sunrpc_net_ops Kirill Tkhai
2018-03-26 9:29 ` Kirill Tkhai [this message]
2018-03-26 9:29 ` [PATCH net-next v1 4/4] net: Convert nfs4blocklayout_net_ops Kirill Tkhai
2018-03-26 17:03 ` [PATCH net-next v1 0/4] Converting pernet_operations (part #7.1) David Miller
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=152205654436.6058.5257383048557457339.stgit@localhost.localdomain \
--to=ktkhai@virtuozzo.com \
--cc=anna.schumaker@netapp.com \
--cc=davem@davemloft.net \
--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