Subject: Re: possible circular locking dependency detected

From: Al Viro <[email-masked]>
Date: Fri, 2 Sep 2016 18:53:48 +0100

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...