Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757011AbYJQQlj (ORCPT ); Fri, 17 Oct 2008 12:41:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755516AbYJQQlU (ORCPT ); Fri, 17 Oct 2008 12:41:20 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:48648 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755440AbYJQQlT (ORCPT ); Fri, 17 Oct 2008 12:41:19 -0400 Date: Fri, 17 Oct 2008 12:41:16 -0400 From: Christoph Hellwig To: Alexander Beregalov Cc: xfs@oss.sgi.com, linux-next@vger.kernel.org, LKML Subject: Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17) Message-ID: <20081017164116.GA17375@infradead.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 837 Lines: 19 On Fri, Oct 17, 2008 at 04:43:07PM +0400, Alexander Beregalov wrote: > It is SMP x86_64, rootfs is on XFS The message comes from code in XFS, but I really wonder where the atomic context comes from. xfs_iget_core has a few changes in the tree pulled into todays Linux-next, but it's still missing the recent updates redoing this area completely. In some ways it looks like this process has the the atomic context flag left pending somewhere, but that should also trigger warnings on the VFS locks like i_mutex. Very misterious. IS there a specific workload you can reproduce this with? -- 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/