netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: davem@davemloft.net, pablo@netfilter.org,
	kadlec@blackhole.kfki.hu, fw@strlen.de, netdev@vger.kernel.org,
	ktkhai@virtuozzo.com
Subject: [PATCH net-next 15/16] net: Convert ipv4_net_ops
Date: Wed, 07 Mar 2018 12:41:16 +0300	[thread overview]
Message-ID: <152041567627.11627.13235025320615621828.stgit@localhost.localdomain> (raw)
In-Reply-To: <152041531893.11627.15708076126889316570.stgit@localhost.localdomain>

These pernet_operations register and unregister bunch
of nf_conntrack_l4proto. Exit method unregisters related
sysctl, init method calls init_net and get_net_proto.
The whole builtin_l4proto4 array has pretty simple
init_net and get_net_proto methods. The first one register
sysctl table, the second one is just RO memory dereference.
So, these pernet_operations are safe to be marked as async.

Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
---
 net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c |    1 +
 1 file changed, 1 insertion(+)

diff --git a/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c b/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c
index b50721d9d30e..6531f69db010 100644
--- a/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c
+++ b/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c
@@ -399,6 +399,7 @@ static struct pernet_operations ipv4_net_ops = {
 	.exit = ipv4_net_exit,
 	.id = &conntrack4_net_id,
 	.size = sizeof(struct conntrack4_net),
+	.async = true,
 };
 
 static int __init nf_conntrack_l3proto_ipv4_init(void)

  parent reply	other threads:[~2018-03-07  9:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07  9:38 [PATCH net-next 00/16] Converting pernet_operations (part #5) Kirill Tkhai
2018-03-07  9:39 ` [PATCH net-next 01/16] net: Convert ip6 tables pernet_operations Kirill Tkhai
2018-03-07  9:39 ` [PATCH net-next 02/16] net: Convert xfrm_user_net_ops Kirill Tkhai
2018-03-07  9:39 ` [PATCH net-next 03/16] net: Convert nf_tables_net_ops Kirill Tkhai
2018-03-07  9:39 ` [PATCH net-next 04/16] net: Convert nfnetlink_net_ops Kirill Tkhai
2018-03-07  9:39 ` [PATCH net-next 05/16] net: Convert nfnl_acct_ops Kirill Tkhai
2018-03-07  9:39 ` [PATCH net-next 06/16] net: Convert cttimeout_ops Kirill Tkhai
2018-03-07  9:40 ` [PATCH net-next 07/16] net: Convert nfnl_log_net_ops Kirill Tkhai
2018-03-07  9:40 ` [PATCH net-next 08/16] net: Convert nfnl_queue_net_ops Kirill Tkhai
2018-03-07  9:40 ` [PATCH net-next 09/16] net: Convert pg_net_ops Kirill Tkhai
2018-03-07  9:40 ` [PATCH net-next 10/16] net: Convert arptable_filter_net_ops Kirill Tkhai
2018-03-07  9:40 ` [PATCH net-next 11/16] net: Convert iptable_mangle_net_ops Kirill Tkhai
2018-03-07  9:40 ` [PATCH net-next 12/16] net: Convert iptable_nat_net_ops Kirill Tkhai
2018-03-07  9:40 ` [PATCH net-next 13/16] net: Convert iptable_raw_net_ops Kirill Tkhai
2018-03-07  9:41 ` [PATCH net-next 14/16] net: Convert iptable_security_net_ops Kirill Tkhai
2018-03-07  9:41 ` Kirill Tkhai [this message]
2018-03-07  9:41 ` [PATCH net-next 16/16] net: Convet ipv6_net_ops Kirill Tkhai
2018-03-08 17:40 ` [PATCH net-next 00/16] Converting pernet_operations (part #5) 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=152041567627.11627.13235025320615621828.stgit@localhost.localdomain \
    --to=ktkhai@virtuozzo.com \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.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 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).