[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <565F2726.2080300@pmhahn.de>
Date: Wed, 02 Dec 2015 18:15:18 +0100
From: Philipp Hahn <pmhahn@...ahn.de>
To: Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Florian Weimer <fweimer@...hat.com>
CC: Thomas Gleixner <tglx@...utronix.de>, netdev@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
herbert@...dor.apana.org.au
Subject: Re: Asterisk deadlocks since Kernel 4.1
Hi,
Am 02.12.2015 um 10:45 schrieb Stefan Priebe - Profihost AG:
> here are the results.
>
> It works with 4.1.
> It works with 4.2.
> It does not work with 4.1.13.
the patches were first commitet in v4.3-rc3 and appear as backports only
since v4.2.3 and v4.1.10
> git bisect tells me it stopped working after those two commits were applied:
>
> commit d48623677191e0f035d7afd344f92cf880b01f8e
> Author: Herbert Xu <herbert@...dor.apana.org.au>
> Date: Tue Sep 22 11:38:56 2015 +0800
>
> netlink: Replace rhash_portid with bound
>
> commit 4e27762417669cb459971635be550eb7b5598286
> Author: Herbert Xu <herbert@...dor.apana.org.au>
> Date: Fri Sep 18 19:16:50 2015 +0800
>
> netlink: Fix autobind race condition that leads to zero port ID
I identified the same two patches for our prpblem; see mail from
2015-11-17 16:53 with subject "Strange PF_NETLINK NETLINK_ROUTE stall:
netlink: Fix autobind race condition that leads to zero port ID"
<http://marc.info/?l=linux-kernel&m=144863837825887&w=2>
Philipp
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists