| To: | Alexander Beregalov <a.beregalov@xxxxxxxxx> |
|---|---|
| Subject: | Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17) |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Fri, 17 Oct 2008 16:37:10 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-next@xxxxxxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <a4423d670810171013g5bc19c1cm3f7d9c014ee70349@mail.gmail.com> |
| References: | <a4423d670810170543vd6b4c39p44bf125610d8540@mail.gmail.com> <20081017164116.GA17375@infradead.org> <a4423d670810170954h7ca130aaw8895380a4c6b125@mail.gmail.com> <20081017165738.GA20818@infradead.org> <a4423d670810171013g5bc19c1cm3f7d9c014ee70349@mail.gmail.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
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. |
| Previous by Date: | Returned mail: see transcript for details, Mail Delivery Subsystem |
|---|---|
| Next by Date: | Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17), Arjan van de Ven |
| Previous by Thread: | Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17), Alexander Beregalov |
| Next by Thread: | Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17), Arjan van de Ven |
| Indexes: | [Date] [Thread] [Top] [All Lists] |