Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758520AbbKSMlp (ORCPT ); Thu, 19 Nov 2015 07:41:45 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:56654 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758468AbbKSMln (ORCPT ); Thu, 19 Nov 2015 07:41:43 -0500 Message-Id: <1447936902.1986892.444251921.3928A049@webmail.messagingengine.com> X-Sasl-Enc: 8fdyE70V4uExhtjMCDk9gPcXbUZWNK+ksQ9QmpB/GHDy 1447936902 From: Hannes Frederic Sowa To: "Stefan Priebe - Profihost AG" , Florian Weimer Cc: Thomas Gleixner , netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-dab2dbe4 Subject: Re: Asterisk deadlocks since Kernel 4.1 Date: Thu, 19 Nov 2015 13:41:42 +0100 In-Reply-To: <564DB5F5.9060208@profihost.ag> 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> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1123 Lines: 32 On Thu, Nov 19, 2015, at 12:43, Stefan Priebe - Profihost AG wrote: > > Am 19.11.2015 um 12:41 schrieb Hannes Frederic Sowa: > > On Thu, Nov 19, 2015, at 10:56, Stefan Priebe - Profihost AG wrote: > >> OK it had a livelock again. It just took more time. > >> > >> So here is the data: > > > > Thanks, I couldn't reproduce it so far with simple threaded resolver > > loop on your kernel. :/ > > > > Your data is useless if you don't also provide the file descriptor which > > you are blocking on right now. ;) > > > > Thanks, > > Hannes > > ah sorry. So we need the gdb backtrace with the rcvmsg and then the fd > list + netlink list? Yes, albeit the probability we find something new is minimal. We already know it blocks deep down in netlink code. I tried to reproduce it in multithreaded environment with no results so far. Can you even try a newer kernel? Bye, 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/