From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: possible circular locking dependency detected Date: Fri, 2 Sep 2016 18:53:48 +0100 Message-ID: <20160902175347.GW2356@ZenIV.linux.org.uk> References: <20160901210142.GS2356@ZenIV.linux.org.uk> <87lgzae3f7.fsf@doppelsaurus.mobileactivedefense.com> <20160902160026.GT2356@ZenIV.linux.org.uk> <87d1kme10a.fsf@doppelsaurus.mobileactivedefense.com> <20160902170256.GU2356@ZenIV.linux.org.uk> <8737lib3o4.fsf@doppelsaurus.mobileactivedefense.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , CAI Qian , Miklos Szeredi , Hannes Frederic Sowa , Eric Sandeen , Network Development To: Rainer Weikusat Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:59450 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751335AbcIBRxx (ORCPT ); Fri, 2 Sep 2016 13:53:53 -0400 Content-Disposition: inline In-Reply-To: <8737lib3o4.fsf@doppelsaurus.mobileactivedefense.com> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, Sep 02, 2016 at 06:40:59PM +0100, Rainer Weikusat wrote: > The original deadlock occurred because of some code path locking the > superblock followed by trying to acquire the af_unix readlock while Not even that - one code path takes ->readlock under pipe lock, while another takes pipe lock under sb_start_write...