# Re: \[PATCH 2/2\] af\_unix: split 'u-\>readlock' into two: 'iolock' and 'bindlock'

- From: David Miller \<davem@davemloft.net\>
- Date: 2016-09-02 19:15:36 
- List: netdev
- Page: https://ratatoskr.run/netdev/2016/09/11027717
- Thread: https://ratatoskr.run/netdev/2016/09/11027709/t.md

```text
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Fri, 2 Sep 2016 11:17:18 -0700

> Oh, this was missing a
> 
>   Reported-and-tested-by: CAI Qian [ref]
> 
> who found the new deadlock.
> 
> There's now *another* lockdep deadlock report by him, but that one has
> nothing to do with networking.
> 
> (And neither of these deadlocks will actually deadlock the machine in
> practice, but you can trigger the lockdep reports with some odd splice
> patterns and overlayfs use)

I read over this and can't find any problems.

The main thing I was concerned about was an I/O path that really
expects the socket's hash not to change for whatever reason, but even
all of the unix_find_other() calls are done outside of the mutex
already.
```