| 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 12:41:16 -0400 |
| Cc: | xfs@xxxxxxxxxxx, linux-next@xxxxxxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <a4423d670810170543vd6b4c39p44bf125610d8540@xxxxxxxxxxxxxx> |
| References: | <a4423d670810170543vd6b4c39p44bf125610d8540@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
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? |
| Previous by Date: | Re: XFS filesystem corruption on the arm(el) architecture, Eric Sandeen |
|---|---|
| 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), Alexander Beregalov |
| Previous by Thread: | 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), Alexander Beregalov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |