Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758176AbYJTRWu (ORCPT ); Mon, 20 Oct 2008 13:22:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755990AbYJTRNJ (ORCPT ); Mon, 20 Oct 2008 13:13:09 -0400 Received: from mail-gx0-f16.google.com ([209.85.217.16]:47180 "EHLO mail-gx0-f16.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756077AbYJTRNH (ORCPT ); Mon, 20 Oct 2008 13:13:07 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=JUxsAQxHcYtN8o3lU7q6hwafXXZtNbwSa2nnWdn97an2DoPQm/L0Jz89e7OJ/Bjz++ LAC/v3EIdJD3qVqMaNxvyn2UiesjcCSkwCBfZKYnHUGS8Z68pizos6mpVVXKorVeF0FP gNLszNUCltzLDEuX7rms3609ORC87EuJb+JXQ= Message-ID: Date: Mon, 20 Oct 2008 21:13:05 +0400 From: "Alexander Beregalov" To: "Christoph Hellwig" Subject: Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17) Cc: "Arjan van de Ven" , xfs@oss.sgi.com, linux-next@vger.kernel.org, LKML In-Reply-To: <20081020163327.GA15651@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081017164116.GA17375@infradead.org> <20081017165738.GA20818@infradead.org> <20081017203710.GA27187@infradead.org> <20081017135510.7127c4e7@infradead.org> <20081020163327.GA15651@infradead.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1135 Lines: 34 2008/10/20 Christoph Hellwig : > On Mon, Oct 20, 2008 at 06:58:09PM +0400, Alexander Beregalov wrote: >> Hi Christoph >> >> I have the same result with next-1020 and today's xfs-2.6.git/master >> ( >> commit bfd2bd10da76378dc4afd87d7d204a1d3d70b347 >> Author: David Chinner >> Date: Fri Oct 17 15:36:23 2008 +1000 >> Inode: Allow external list initialisation >> ) Ha, that kernel (xfs/master) has made my system dead locked. SysRQ-d: Show all locks held in the system 1 lock held by pdflush (&type->s_umount_key#18{----}, at writeback_inodes 1 lock held by login (&(&ip->i_iolock)->mr_lock){----} at xfs_ilock and so on ( many locks at xfs_ilock) >> >> Should I start bisecting? > > That would be extremely helpful! > > > And as mentioned in the other mail I still can't reproduce it, but I can > currently only test on x86-32, not x86-64. > -- 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/