From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967075AbbLQP2i (ORCPT ); Thu, 17 Dec 2015 10:28:38 -0500 Received: from tiger.mobileactivedefense.com ([217.174.251.109]:33795 "EHLO tiger.mobileactivedefense.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934373AbbLQP2g (ORCPT ); Thu, 17 Dec 2015 10:28:36 -0500 From: Rainer Weikusat To: Hannes Frederic Sowa Cc: David Miller , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Al Viro Subject: Re: [PATCH] af_unix: Revert 'lock_interruptible' in stream receive code In-Reply-To: <56727EE9.5020805@stressinduktion.org> (Hannes Frederic Sowa's message of "Thu, 17 Dec 2015 10:22:49 +0100") References: <877fke6tqi.fsf@doppelsaurus.mobileactivedefense.com> <56727EE9.5020805@stressinduktion.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Date: Thu, 17 Dec 2015 15:28:21 +0000 Message-ID: <87a8p92iy2.fsf@doppelsaurus.mobileactivedefense.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (tiger.mobileactivedefense.com [217.174.251.109]); Thu, 17 Dec 2015 15:28:29 +0000 (GMT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hannes Frederic Sowa writes: > On 16.12.2015 21:09, Rainer Weikusat wrote: >> With b3ca9b02b00704053a38bfe4c31dbbb9c13595d0, the AF_UNIX SOCK_STREAM >> receive code was changed from using mutex_lock(&u->readlock) to >> mutex_lock_interruptible(&u->readlock) to prevent signals from being >> delayed for an indefinite time if a thread sleeping on the mutex >> happened to be selected for handling the signal. But this was never a >> problem with the stream receive code (as opposed to its datagram >> counterpart) as that never went to sleep waiting for new messages with the >> mutex held and thus, wouldn't cause secondary readers to block on the >> mutex waiting for the sleeping primary reader. As the interruptible >> locking makes the code more complicated in exchange for no benefit, >> change it back to using mutex_lock. >> >> Signed-off-by: Rainer Weikusat >> --- >> >> Considering that the datagram receive routine also doesn't go the sleep >> with the mutex held anymore, the 37ab4fa7844a044dc21fde45e2a0fc2f3c3b6490 >> change to unix_autobind is now similarly purposeless. > > I wouldn't do this conversion, yet. There is still a deadlock lingering > around which should be solved earlier: > > http://lists.openwall.net/netdev/2015/11/10/4 > > Unfortunately I haven't found a good way how to solve it, yet. Judging from the link, that's not related to the stream receive code.