These pernet_operations just create and destroy /proc entries.
Also, new /proc entries also may come after new nf rules
are added, but this is not possible, when net isn't alive.
So, they are safe to be marked as async.

Signed-off-by: Kirill Tkhai <ktk...@virtuozzo.com>
---
 net/netfilter/xt_hashlimit.c |    1 +
 net/netfilter/xt_recent.c    |    1 +
 2 files changed, 2 insertions(+)

diff --git a/net/netfilter/xt_hashlimit.c b/net/netfilter/xt_hashlimit.c
index ca6847403ca2..53889a7bf91d 100644
--- a/net/netfilter/xt_hashlimit.c
+++ b/net/netfilter/xt_hashlimit.c
@@ -1343,6 +1343,7 @@ static struct pernet_operations hashlimit_net_ops = {
        .exit   = hashlimit_net_exit,
        .id     = &hashlimit_net_id,
        .size   = sizeof(struct hashlimit_net),
+       .async  = true,
 };
 
 static int __init hashlimit_mt_init(void)
diff --git a/net/netfilter/xt_recent.c b/net/netfilter/xt_recent.c
index 245fa350a7a8..d25cede62cb1 100644
--- a/net/netfilter/xt_recent.c
+++ b/net/netfilter/xt_recent.c
@@ -689,6 +689,7 @@ static struct pernet_operations recent_net_ops = {
        .exit   = recent_net_exit,
        .id     = &recent_net_id,
        .size   = sizeof(struct recent_net),
+       .async  = true,
 };
 
 static struct xt_match recent_mt_reg[] __read_mostly = {

Reply via email to