----- Original Message -----
> From: "Linus Torvalds" <torva...@linux-foundation.org>
> To: "Al Viro" <v...@zeniv.linux.org.uk>, "CAI Qian" <caiq...@redhat.com>
> Cc: "Miklos Szeredi" <mik...@szeredi.hu>, "Rainer Weikusat"
> <rweiku...@cyberadapt.com>, "Hannes Frederic Sowa"
> <han...@stressinduktion.org>, "Rainer Weikusat"
> <rweiku...@mobileactivedefense.com>, "Eric Sandeen"
> <esand...@redhat.com>, "Network Development" <netdev@vger.kernel.org>
> Sent: Thursday, September 1, 2016 6:04:38 PM
> Subject: Re: possible circular locking dependency detected
>
> On Thu, Sep 1, 2016 at 2:43 PM, Linus Torvalds
> <torva...@linux-foundation.org> wrote:
> > On Thu, Sep 1, 2016 at 2:01 PM, Al Viro <v...@zeniv.linux.org.uk> wrote:
> >>
> >> Outside as in "all fs activity in bind happens under it". Along with
> >> assignment to ->u.addr, etc. IOW, make it the outermost lock there.
> >
> > Hah, yes. I misunderstood you.
> >
> > Yes. In fact that fixes the problem I mentioned, rather than introducing
> > it.
>
> So the easiest approach would seem to be to revert commit c845acb324aa
> ("af_unix: Fix splice-bind deadlock"), and then apply the lock split.
>
> Like the attached two patches.
>
> This is still *entirely* untested.
Tested-by: CAI Qian <caiq...@redhat.com>
>
> Rainer?
>
> Linus
>
