From: Philipp Hahn <pmhahn@pmhahn•de>
To: Stefan Priebe <s.priebe@profihost•ag>,
Herbert Xu <herbert@gondor•apana.org.au>
Cc: Hannes Frederic Sowa <hannes@stressinduktion•org>,
Florian Weimer <fweimer@redhat•com>,
Thomas Gleixner <tglx@linutronix•de>,
netdev@vger•kernel.org, linux-fsdevel@vger•kernel.org,
linux-kernel@vger•kernel.org,
jannik Winkel <j.winkel@profihost•ag>,
Marco Schinkel <m.schinkel@profihost•ag>
Subject: Re: Asterisk deadlocks since Kernel 4.1
Date: Mon, 7 Dec 2015 08:41:38 +0100 [thread overview]
Message-ID: <56653832.2030607@pmhahn.de> (raw)
In-Reply-To: <5664A102.2030602@profihost.ag>
Hello Stefan,
Am 06.12.2015 um 21:56 schrieb Stefan Priebe:
> i think i found the issue in 4.1 with netlink. Somebody made a mistake
> while backporting or cherry-picking your patch "netlink: Fix autobind
> race condition that leads to zero port ID" to 4.1.
>
> It misses a goto in 4.1.
>
> This goto is missing in 4.1:
>
> diff --git a/net/netlink/af_netlink.c b/net/netlink/af_netlink.c
> index 4017e12..f15c001 100644
> --- a/net/netlink/af_netlink.c
> +++ b/net/netlink/af_netlink.c
> @@ -1132,7 +1132,6 @@ static int netlink_insert(struct sock *sk, u32
> portid)
> if (err == -EEXIST)
> err = -EADDRINUSE;
> sock_put(sk);
> - goto err;
> }
>
> /* We need to ensure that the socket is hashed and visible. */
>
> Can you please confirm, that this is not correct and might cause those
> issues.
I just tested that patch and it seems to fix our hang. Thank you for
your good work.
Philipp
PS: I guess I can skip testing your other test request as this simple
patch is part of your other hiuq4bsW patch. If I should still test it,
just send a note.
next prev parent reply other threads:[~2015-12-07 7:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <564B3D35.50004@profihost.ag>
[not found] ` <alpine.DEB.2.11.1511171936030.3761@nanos>
2015-11-17 19:27 ` Asterisk deadlocks since Kernel 4.1 Stefan Priebe
2015-11-17 19:43 ` Thomas Gleixner
2015-11-18 20:23 ` Stefan Priebe
2015-11-18 21:00 ` Hannes Frederic Sowa
2015-11-18 21:20 ` Stefan Priebe
2015-11-18 21:22 ` Hannes Frederic Sowa
2015-11-19 9:35 ` Stefan Priebe - Profihost AG
2015-11-18 21:18 ` Florian Weimer
2015-11-18 21:23 ` Stefan Priebe
2015-11-19 9:39 ` Florian Weimer
2015-11-18 21:36 ` Stefan Priebe
2015-11-18 21:40 ` Hannes Frederic Sowa
2015-11-18 21:42 ` Stefan Priebe
2015-11-18 21:58 ` Hannes Frederic Sowa
2015-11-19 9:44 ` Florian Weimer
2015-11-19 9:49 ` Stefan Priebe - Profihost AG
2015-11-19 9:56 ` Stefan Priebe - Profihost AG
2015-11-19 11:41 ` Hannes Frederic Sowa
2015-11-19 11:43 ` Stefan Priebe - Profihost AG
2015-11-19 12:41 ` Hannes Frederic Sowa
2015-11-19 12:46 ` Stefan Priebe - Profihost AG
2015-11-19 13:19 ` Florian Weimer
2015-11-19 19:51 ` Stefan Priebe
2015-11-23 12:44 ` Stefan Priebe - Profihost AG
2015-11-23 12:57 ` Hannes Frederic Sowa
2015-11-24 13:35 ` Stefan Priebe - Profihost AG
2015-12-02 9:45 ` Stefan Priebe - Profihost AG
2015-12-02 11:40 ` Hannes Frederic Sowa
2015-12-02 17:51 ` Philipp Hahn
2015-12-03 8:23 ` Stefan Priebe - Profihost AG
2015-12-04 18:26 ` Stefan Priebe
2015-12-05 1:08 ` Herbert Xu
2015-12-06 20:56 ` Stefan Priebe
2015-12-07 1:20 ` Herbert Xu
2015-12-07 6:58 ` Stefan Priebe - Profihost AG
2015-12-08 6:13 ` netlink: Add missing goto statement to netlink_insert Herbert Xu
2015-12-08 16:21 ` David Miller
2015-12-09 3:29 ` Greg KH
2015-12-07 7:41 ` Philipp Hahn [this message]
2015-12-05 14:19 ` Asterisk deadlocks since Kernel 4.1 Philipp Matthias Hahn
2015-12-05 15:34 ` Stefan Priebe
2015-12-02 17:15 ` Philipp Hahn
2015-12-02 18:23 ` Hannes Frederic Sowa
2015-11-17 14:46 Stefan Priebe - Profihost AG
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=56653832.2030607@pmhahn.de \
--to=pmhahn@pmhahn$(echo .)de \
--cc=fweimer@redhat$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=j.winkel@profihost$(echo .)ag \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=m.schinkel@profihost$(echo .)ag \
--cc=netdev@vger$(echo .)kernel.org \
--cc=s.priebe@profihost$(echo .)ag \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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