Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964936AbbLBSXs (ORCPT ); Wed, 2 Dec 2015 13:23:48 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:35309 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753431AbbLBSXq (ORCPT ); Wed, 2 Dec 2015 13:23:46 -0500 Message-Id: <1449080605.3845593.456079161.39E78A8D@webmail.messagingengine.com> X-Sasl-Enc: MQSXNCOsG4L2OIVb8YBxl5rX42EuBmXcmWrsH/QSf2aj 1449080605 From: Hannes Frederic Sowa To: Philipp Hahn , "Stefan Priebe - Profihost AG" , Florian Weimer Cc: Thomas Gleixner , netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, herbert@gondor.apana.org.au MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-b94e6169 Subject: Re: Asterisk deadlocks since Kernel 4.1 Date: Wed, 02 Dec 2015 19:23:25 +0100 In-Reply-To: <565F2726.2080300@pmhahn.de> References: <564B3D35.50004@profihost.ag> <564B7F9D.5060701@profihost.ag> <564CDE2F.8000201@profihost.ag> <564CEB0C.40006@redhat.com> <564CEF5D.3080005@profihost.ag> <564D9A17.6080305@redhat.com> <564D9B21.302@profihost.ag> <564D9CE6.2090104@profihost.ag> <1447933294.1974772.444210441.67F1AC5E@webmail.messagingengine.com> <564DB5F5.9060208@profihost.ag> <1447936902.1986892.444251921.3928A049@webmail.messagingengine.com> <564DC4A5.70104@profihost.ag> <564DCC4C.1090009@redhat.com> <564E2852.8000200@profihost.ag> <56530A42.6030609@profihost.ag> <1448283451.4019628.447573353.3659E447@webmail.messagingengine.com> <565EBDC1.1090808@profihost.ag> <565F2726.2080300@pmhahn.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1535 Lines: 45 Hello, On Wed, Dec 2, 2015, at 18:15, Philipp Hahn wrote: > 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 > > Date: Tue Sep 22 11:38:56 2015 +0800 > > > > netlink: Replace rhash_portid with bound > > > > commit 4e27762417669cb459971635be550eb7b5598286 > > Author: Herbert Xu > > 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" > > Thanks, I missed this mail. I have a further look. I couldn't reproduce it myself but will check if your test program does it. Thanks a lot, Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/