From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: davem@davemloft.net, vyasevich@gmail.com, nhorman@tuxdriver.com,
jon.maloy@ericsson.com, ying.xue@windriver.com,
santosh.shilimkar@oracle.com, netdev@vger.kernel.org,
ktkhai@virtuozzo.com
Subject: [PATCH net-next 2/4] net: Convert sctp_ctrlsock_ops
Date: Tue, 13 Mar 2018 13:37:02 +0300 [thread overview]
Message-ID: <152093742247.31266.12266517837915305348.stgit@localhost.localdomain> (raw)
In-Reply-To: <152093726634.31266.4973922580771632781.stgit@localhost.localdomain>
These pernet_operations create and destroy net::sctp::ctl_sock.
Since pernet_operations do not send sctp packets each other,
they look safe to be marked as async.
Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
---
net/sctp/protocol.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/sctp/protocol.c b/net/sctp/protocol.c
index 32be52304f98..606361ee9e4a 100644
--- a/net/sctp/protocol.c
+++ b/net/sctp/protocol.c
@@ -1354,6 +1354,7 @@ static void __net_init sctp_ctrlsock_exit(struct net *net)
static struct pernet_operations sctp_ctrlsock_ops = {
.init = sctp_ctrlsock_init,
.exit = sctp_ctrlsock_exit,
+ .async = true,
};
/* Initialize the universe into something sensible. */
next prev parent reply other threads:[~2018-03-13 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 10:36 [PATCH net-next 0/4] Converting pernet_operations (part #6) Kirill Tkhai
2018-03-13 10:36 ` [PATCH net-next 1/4] net: Convert sctp_defaults_ops Kirill Tkhai
2018-03-13 10:37 ` Kirill Tkhai [this message]
2018-03-13 11:45 ` [PATCH net-next 2/4] net: Convert sctp_ctrlsock_ops Neil Horman
2018-03-13 10:37 ` [PATCH net-next 3/4] net: Convert tipc_net_ops Kirill Tkhai
2018-03-13 10:37 ` [PATCH net-next 4/4] net: Convert rds_tcp_net_ops Kirill Tkhai
2018-03-13 15:25 ` [PATCH net-next 0/4] Converting pernet_operations (part #6) 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=152093742247.31266.12266517837915305348.stgit@localhost.localdomain \
--to=ktkhai@virtuozzo.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=santosh.shilimkar@oracle.com \
--cc=vyasevich@gmail.com \
--cc=ying.xue@windriver.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