From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932966AbcLIAJR (ORCPT ); Thu, 8 Dec 2016 19:09:17 -0500 Received: from mail-yw0-f194.google.com ([209.85.161.194]:36075 "EHLO mail-yw0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752431AbcLIAJN (ORCPT ); Thu, 8 Dec 2016 19:09:13 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Cong Wang Date: Thu, 8 Dec 2016 16:08:27 -0800 Message-ID: Subject: Re: fs, net: deadlock between bind/splice on af_unix To: Dmitry Vyukov Cc: Al Viro , "linux-fsdevel@vger.kernel.org" , LKML , David Miller , Rainer Weikusat , Hannes Frederic Sowa , netdev , Eric Dumazet , syzkaller Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 8, 2016 at 8:30 AM, Dmitry Vyukov wrote: > Chain exists of: > Possible unsafe locking scenario: > > CPU0 CPU1 > ---- ---- > lock(sb_writers#5); > lock(&u->bindlock); > lock(sb_writers#5); > lock(&pipe->mutex/1); This looks false positive, probably just needs lockdep_set_class() to set keys for pipe->mutex and unix->bindlock.