public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: pablo@netfilter.org, kadlec@blackhole.kfki.hu, fw@strlen.de,
	stephen@networkplumber.org, davem@davemloft.net,
	dmitry.tarnyagin@lockless.no, socketcan@hartkopp.net,
	mkl@pengutronix.de, gerrit@erg.abdn.ac.uk,
	yoshfuji@linux-ipv6.org, johannes.berg@intel.com,
	garsilva@embeddedor.com, ross.lagerwall@citrix.com,
	aconole@bytheb.org, netdev@vger.kernel.org, ktkhai@virtuozzo.com
Subject: [PATCH net-next 05/12] net: Convert cangw_pernet_ops
Date: Mon, 05 Mar 2018 14:31:19 +0300	[thread overview]
Message-ID: <152024947909.3454.8970091597212014813.stgit@localhost.localdomain> (raw)
In-Reply-To: <152024910817.3454.18426950407771593279.stgit@localhost.localdomain>

These pernet_operations have a deal with cgw_list,
and the rest of accesses are made under rtnl_lock().
The only exception is cgw_dump_jobs(), which is
accessed under rcu_read_lock(). cgw_dump_jobs() is
called on netlink request, and it does not seem,
foreign pernet_operations want to send a net such
the messages. So, we mark them as async.

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

diff --git a/net/can/gw.c b/net/can/gw.c
index 398dd0395ad9..08e97668d5cf 100644
--- a/net/can/gw.c
+++ b/net/can/gw.c
@@ -1010,6 +1010,7 @@ static void __net_exit cangw_pernet_exit(struct net *net)
 static struct pernet_operations cangw_pernet_ops = {
 	.init = cangw_pernet_init,
 	.exit = cangw_pernet_exit,
+	.async = true,
 };
 
 static __init int cgw_module_init(void)

  parent reply	other threads:[~2018-03-05 11:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 11:30 [PATCH net-next 00/12] Converting pernet_operations (part #4) Kirill Tkhai
2018-03-05 11:30 ` [PATCH net-next 01/12] net: Convert broute_net_ops, frame_filter_net_ops and frame_nat_net_ops Kirill Tkhai
2018-03-05 11:30 ` [PATCH net-next 02/12] net: Convert log pernet_operations Kirill Tkhai
2018-03-05 11:31 ` [PATCH net-next 03/12] net: Convert arp_tables_net_ops and ip6_tables_net_ops Kirill Tkhai
2018-03-05 11:31 ` [PATCH net-next 04/12] net: Convert caif_net_ops Kirill Tkhai
2018-03-05 11:31 ` Kirill Tkhai [this message]
2018-03-05 11:31 ` [PATCH net-next 06/12] net: Convert dccp_v4_ops Kirill Tkhai
2018-03-05 11:31 ` [PATCH net-next 07/12] net: Convert dccp_v6_ops Kirill Tkhai
2018-03-05 11:31 ` [PATCH net-next 08/12] net: Convert fou_net_ops Kirill Tkhai
2018-03-05 11:31 ` [PATCH net-next 09/12] net: Convert ip_set_net_ops Kirill Tkhai
2018-03-05 11:32 ` [PATCH net-next 10/12] net: Convert nf_conntrack_net_ops Kirill Tkhai
2018-03-05 11:32 ` [PATCH net-next 11/12] net: Convert ctnetlink_net_ops Kirill Tkhai
2018-03-05 11:32 ` [PATCH net-next 12/12] net: Convert proto_gre_net_ops Kirill Tkhai
2018-03-05 15:53 ` [PATCH net-next 00/12] Converting pernet_operations (part #4) 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=152024947909.3454.8970091597212014813.stgit@localhost.localdomain \
    --to=ktkhai@virtuozzo.com \
    --cc=aconole@bytheb.org \
    --cc=davem@davemloft.net \
    --cc=dmitry.tarnyagin@lockless.no \
    --cc=fw@strlen.de \
    --cc=garsilva@embeddedor.com \
    --cc=gerrit@erg.abdn.ac.uk \
    --cc=johannes.berg@intel.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=ross.lagerwall@citrix.com \
    --cc=socketcan@hartkopp.net \
    --cc=stephen@networkplumber.org \
    --cc=yoshfuji@linux-ipv6.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