From: Florian Westphal <fw@strlen.de>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
Juliana Rodrigueiro <juliana.rodrigueiro@intra2net.com>
Subject: Re: 4.19: Traced deadlock during xfrm_user module load
Date: Tue, 25 Jun 2019 18:53:44 +0200 [thread overview]
Message-ID: <20190625165344.ii4zgvxydqj663ny@breakpoint.cc> (raw)
In-Reply-To: <20190625155509.pgcxwgclqx3lfxxr@intra2net.com>
Thomas Jarosch <thomas.jarosch@intra2net.com> wrote:
> we're in the process of upgrading to kernel 4.19 and hit
> a very rare lockup on boot during "xfrm_user" module load.
> The tested kernel was 4.19.55.
>
> When the strongswan IPsec service starts, it loads the xfrm_user module.
> -> modprobe hangs forever.
>
> Also network services like ssh or apache stop responding,
> ICMP ping still works.
>
> By chance we had magic sysRq enabled and were able to get some meaningful stack
> traces. We've rebuilt the kernel with LOCKDEP + DEBUG_INFO + DEBUG_INFO_REDUCED,
> but so far failed to reproduce the issue even when hammering the suspected
> deadlock case. Though it's just hammering it for a few hours yet.
>
> Preliminary analysis:
>
> "modprobe xfrm_user":
> xfrm_user_init()
> register_pernet_subsys()
> -> grab pernet_ops_rwsem
> ..
> netlink_table_grab()
> calls schedule() as "nl_table_users" is non-zero
>
>
> conntrack netlink related program "info_iponline" does this in parallel:
> netlink_bind()
> netlink_lock_table() -> increases "nl_table_users"
> nfnetlink_bind()
> # does not unlock the table as it's locked by netlink_bind()
> __request_module()
> call_usermodehelper_exec()
>
>
> "modprobe nf_conntrack_netlink" runs and inits nf_conntrack_netlink:
> ctnetlink_init()
> register_pernet_subsys()
> -> blocks on "pernet_ops_rwsem" thanks to xfrm_user module
> -> schedule()
> -> deadlock forever
>
Thanks for this detailed analysis.
In this specific case I think this is enough:
diff --git a/net/netfilter/nfnetlink.c b/net/netfilter/nfnetlink.c
index 92077d459109..61ba92415480 100644
--- a/net/netfilter/nfnetlink.c
+++ b/net/netfilter/nfnetlink.c
@@ -578,7 +578,8 @@ static int nfnetlink_bind(struct net *net, int group)
ss = nfnetlink_get_subsys(type << 8);
rcu_read_unlock();
if (!ss)
- request_module("nfnetlink-subsys-%d", type);
+ request_module_nowait("nfnetlink-subsys-%d", type);
return 0;
}
#endif
next prev parent reply other threads:[~2019-06-25 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 15:55 4.19: Traced deadlock during xfrm_user module load Thomas Jarosch
2019-06-25 16:53 ` Florian Westphal [this message]
2019-06-27 15:46 ` Thomas Jarosch
2019-06-27 15:50 ` Florian Westphal
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=20190625165344.ii4zgvxydqj663ny@breakpoint.cc \
--to=fw@strlen.de \
--cc=juliana.rodrigueiro@intra2net.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=thomas.jarosch@intra2net.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