From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751268AbbIYFeZ (ORCPT ); Fri, 25 Sep 2015 01:34:25 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:56890 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750850AbbIYFeY (ORCPT ); Fri, 25 Sep 2015 01:34:24 -0400 Subject: Re: Glibc recvmsg from kernel netlink socket hangs forever To: Herbert Xu References: <20150925043653.GA29111@roeck-us.net> <20150925045853.GA5286@gondor.apana.org.au> Cc: Steven Schlansker , linux-kernel@vger.kernel.org, Eric Dumazet , netdev@vger.kernel.org From: Guenter Roeck Message-ID: <5604DCD2.4090600@roeck-us.net> Date: Thu, 24 Sep 2015 22:34:10 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150925045853.GA5286@gondor.apana.org.au> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Herbert, On 09/24/2015 09:58 PM, Herbert Xu wrote: > On Thu, Sep 24, 2015 at 09:36:53PM -0700, Guenter Roeck wrote: >> >> http://comments.gmane.org/gmane.linux.network/363085 >> >> might explain your problem. >> >> I thought this was resolved in 4.1, but it looks like the problem still persists >> there. At least I have reports from my workplace that 4.1.6 and 4.1.7 are still >> affected. I don't know if there have been any relevant changes in 4.2. >> >> Copying Herbert and Eric for additional input. > > There was a separate bug discovered by Tejun recently. You need > to apply the patches > > https://patchwork.ozlabs.org/patch/519245/ > https://patchwork.ozlabs.org/patch/520824/ > I assume this is on top of mainline ? > There is another follow-up but it shouldn't make any difference > in practice. > Any idea what may be needed for 4.1 ? I am currently trying https://patchwork.ozlabs.org/patch/473041/, but I have no idea if that will help with the problem we are seeing there. Thanks, Guenter