From: Dave Chinner <david@fromorbit.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Arjan van de Ven <arjan@infradead.org>,
xfs@oss.sgi.com, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
Date: Tue, 21 Oct 2008 09:35:49 +1100 [thread overview]
Message-ID: <20081020223549.GA21152@disturbed> (raw)
In-Reply-To: <a4423d670810201013w6448cb38w402771799cefb5f5@mail.gmail.com>
On Mon, Oct 20, 2008 at 09:13:05PM +0400, Alexander Beregalov wrote:
> 2008/10/20 Christoph Hellwig <hch@infradead.org>:
> > 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 <david@fromorbit.com>
> >> 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)
Curious. Can you post the full stack traces?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-10-20 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 12:43 BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17) Alexander Beregalov
2008-10-17 16:41 ` Christoph Hellwig
2008-10-17 16:54 ` Alexander Beregalov
2008-10-17 16:57 ` Christoph Hellwig
2008-10-17 17:13 ` Alexander Beregalov
2008-10-17 20:37 ` Christoph Hellwig
2008-10-17 20:55 ` Arjan van de Ven
2008-10-20 14:58 ` Alexander Beregalov
2008-10-20 16:33 ` Christoph Hellwig
2008-10-20 17:13 ` Alexander Beregalov
2008-10-20 22:35 ` Dave Chinner [this message]
2008-10-21 11:42 ` Alexander Beregalov
2008-10-22 7:58 ` Dave Chinner
2008-10-22 8:21 ` Alexander Beregalov
2008-10-22 8:28 ` Dave Chinner
2008-10-22 8:25 ` Dave Chinner
2008-10-22 9:12 ` Alexander Beregalov
2008-10-22 10:13 ` Christoph Hellwig
2008-10-22 21:10 ` Dave Chinner
2008-10-22 15:06 ` BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? Johannes Weiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081020223549.GA21152@disturbed \
--to=david@fromorbit.com \
--cc=a.beregalov@gmail.com \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).