[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <152024948834.3454.15662913883647294282.stgit@localhost.localdomain>
Date: Mon, 05 Mar 2018 14:31:28 +0300
From: Kirill Tkhai <ktkhai@...tuozzo.com>
To: pablo@...filter.org, kadlec@...ckhole.kfki.hu, fw@...len.de,
stephen@...workplumber.org, davem@...emloft.net,
dmitry.tarnyagin@...kless.no, socketcan@...tkopp.net,
mkl@...gutronix.de, gerrit@....abdn.ac.uk, yoshfuji@...ux-ipv6.org,
johannes.berg@...el.com, garsilva@...eddedor.com,
ross.lagerwall@...rix.com, aconole@...heb.org,
netdev@...r.kernel.org, ktkhai@...tuozzo.com
Subject: [PATCH net-next 06/12] net: Convert dccp_v4_ops
These pernet_operations create and destroy net::dccp::v4_ctl_sk.
It looks like another pernet_operations don't want to send
dccp packets to dying or creating net. Batch method similar
to ipv4/ipv6 sockets and it has to be safe to be executed
in parallel with anything else. So, we mark them as async.
Signed-off-by: Kirill Tkhai <ktkhai@...tuozzo.com>
---
net/dccp/ipv4.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/dccp/ipv4.c b/net/dccp/ipv4.c
index e65fcb45c3f6..13ad28ab1e79 100644
--- a/net/dccp/ipv4.c
+++ b/net/dccp/ipv4.c
@@ -1031,6 +1031,7 @@ static struct pernet_operations dccp_v4_ops = {
.init = dccp_v4_init_net,
.exit = dccp_v4_exit_net,
.exit_batch = dccp_v4_exit_batch,
+ .async = true,
};
static int __init dccp_v4_init(void)
Powered by blists - more mailing lists