From: Christoph Hellwig <hch@lst.de>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: xfs-masters@oss.sgi.com,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: [xfs-masters] next-20081210: BUG: sleeping function called from invalid context at mm/slub.c:1619 (XFS)
Date: Thu, 11 Dec 2008 19:29:55 +0100 [thread overview]
Message-ID: <20081211182955.GB27952@lst.de> (raw)
In-Reply-To: <a4423d670812110210g50d66304pb0a7d96b3dde00c7@mail.gmail.com>
On Thu, Dec 11, 2008 at 01:10:23PM +0300, Alexander Beregalov wrote:
> BUG: sleeping function called from invalid context at mm/slub.c:1619
> in_atomic(): 1, irqs_disabled(): 0, pid: 8096, name: sh
> INFO: lockdep is turned off.
> Pid: 8096, comm: sh Tainted: G W 2.6.28-rc7-next-20081210 #2
> Call Trace:
> [<ffffffff80256e5a>] ? __debug_show_held_locks+0x1b/0x24
> [<ffffffff8022fb55>] __might_sleep+0x120/0x122
> [<ffffffff8029c526>] __kmalloc+0x70/0xfc
> [<ffffffff803534d2>] kmem_alloc+0x75/0xd7
> [<ffffffff803350ba>] xfs_fs_vcmn_err+0x46/0x94
> [<ffffffff80335297>] xfs_fs_cmn_err+0x59/0x5e
xfs_fs_vcmn_err does a sleeping memory allocation under a spinlock,
nasty. I have an idea that will get rid of the memory allocation
completely, I'll come back to you once I have hacked something up.
> Filesystem "sda2": xlog_space_left: head behind tail
> tail_cycle = 1802201963, tail_bytes = -690563584
> GH cycle = 3078, GH bytes = 69183384
This btw is a bug, too..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-11 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 10:10 next-20081210: BUG: sleeping function called from invalid context at mm/slub.c:1619 (XFS) Alexander Beregalov
2008-12-11 18:29 ` Christoph Hellwig [this message]
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=20081211182955.GB27952@lst.de \
--to=hch@lst.de \
--cc=a.beregalov@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=xfs-masters@oss.sgi.com \
--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