From: Xin Long <lucien....@gmail.com> Date: Sat, 10 Jun 2017 14:56:56 +0800
> Dmitry got the following recursive locking report while running syzkaller > fuzzer, the Call Trace: ... > This warning is caused by the lock held by sctp_getsockopt() is on one > socket, while the other lock that sctp_close() is getting later is on > the newly created (which failed) socket during peeloff operation. > > This patch is to avoid this warning by use lock_sock with subclass > SINGLE_DEPTH_NESTING as Wang Cong and Marcelo's suggestion. > > Reported-by: Dmitry Vyukov <dvyu...@google.com> > Suggested-by: Marcelo Ricardo Leitner <marcelo.leit...@gmail.com> > Suggested-by: Cong Wang <xiyou.wangc...@gmail.com> > Signed-off-by: Xin Long <lucien....@gmail.com> Applied.
