From mboxrd@z Thu Jan 1 00:00:00 1970 From: 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) Date: Fri, 17 Oct 2008 16:37:10 -0400 Message-ID: <20081017203710.GA27187@infradead.org> References: <20081017164116.GA17375@infradead.org> <20081017165738.GA20818@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:56322 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751483AbYJQUhL (ORCPT ); Fri, 17 Oct 2008 16:37:11 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Alexander Beregalov Cc: Christoph Hellwig , xfs@oss.sgi.com, linux-next@vger.kernel.org, LKML I just ran the xfs testsuite over linux-next on qemu (i386), and I can't find anything at all. Really strange. Let's see if this still there with mondays linux-next, and if yes can you just try the xfs patch from the splitout linux-next patches and see if that alone causes it? In fact that might be useful for todays linux-next, too.