Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933215AbbFIPfL (ORCPT ); Tue, 9 Jun 2015 11:35:11 -0400 Received: from mx02.imt-systems.com ([212.224.83.171]:48139 "EHLO mx02.imt-systems.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753167AbbFIPfH (ORCPT ); Tue, 9 Jun 2015 11:35:07 -0400 MIME-Version: 1.0 In-Reply-To: <5576F3DA.7000106@monom.org> References: <5576D3E7.40302@fedoraproject.org> <5576F3DA.7000106@monom.org> Date: Tue, 9 Jun 2015 17:35:04 +0200 Message-ID: Subject: Re: linux 4.1-rc7 deadlock From: Morten Stevens To: Daniel Wagner Cc: linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 0 () Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1059 Lines: 35 2015-06-09 16:10 GMT+02:00 Daniel Wagner : > Hi Morten, Hi Daniel, > On 06/09/2015 01:54 PM, Morten Stevens wrote: >> [ 28.193327] Possible unsafe locking scenario: >> >> [ 28.194297] CPU0 CPU1 >> [ 28.194774] ---- ---- >> [ 28.195254] lock(&mm->mmap_sem); >> [ 28.195709] lock(&xfs_dir_ilock_class); >> [ 28.196174] lock(&mm->mmap_sem); >> [ 28.196654] lock(&isec->lock); >> [ 28.197108] > > [...] > >> Any ideas? > > I think you hit the same problem many have already reported: > > https://lkml.org/lkml/2015/3/30/594 Yes, that sounds very likely. But that was about 1 month ago, so I thought that it has been fixed in the last weeks? Best regards, Morten -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/