From: Randolph Chung <randolph@tausq.org>
To: Helge Deller <deller@gmx.de>
Cc: linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] fix BUG: sleeping function called from invalid context at mm/slab.c:3044
Date: Thu, 18 Dec 2008 18:23:26 +0800 [thread overview]
Message-ID: <494A249E.9070405@tausq.org> (raw)
In-Reply-To: <494983DE.2050105@gmx.de>
i knew there was a reason why this was a stack variable before... ;-)
(of course, that is not ideal either)
randolph
Helge Deller wrote:
> Since unwind_frame_init_from_blocked_task() may be called from
> interrupt/in_atomic context, it needs to kmalloc() memory with
> GFP_ATOMIC instead of GFP_KERNEL.
>
> This fixes this warning (ShowTasks called from sysrq handler):
>
> BUG: sleeping function called from invalid context at mm/slab.c:3044
> in_atomic(): 1, irqs_disabled(): 1, pid: 2119, name: miniruby
> Backtrace:
> [<10132e78>] __might_sleep+0x4c/0x118
> [<1018f644>] kmem_cache_alloc+0x2c/0xb4
> [<1011bae0>] unwind_frame_init_from_blocked_task+0x30/0xa0
> [<1010fd3c>] parisc_show_stack+0x3c/0xac
> [<10132c7c>] show_state_filter+0x80/0xd8
> [<102f4074>] __handle_sysrq+0xd0/0x1b0
> [<102f9558>] receive_chars+0x22c/0x318
> [<102f9940>] serial8250_handle_port+0x40/0x88
> [<102f9a8c>] serial8250_interrupt+0x104/0x10c
> [<10161920>] handle_IRQ_event+0x44/0x94
> [<10161acc>] __do_IRQ+0x15c/0x1dc
> [<102c442c>] superio_interrupt+0x74/0xa8
> [<10161920>] handle_IRQ_event+0x44/0x94
> [<10161acc>] __do_IRQ+0x15c/0x1dc
> [<10110fb4>] do_cpu_irq_mask+0x90/0xbc
> [<10114068>] intr_return+0x0/0x4
>
> Signed-off-by: Helge Deller <deller@gmx.de>
>
prev parent reply other threads:[~2008-12-18 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 22:57 [PATCH] fix BUG: sleeping function called from invalid context at mm/slab.c:3044 Helge Deller
2008-12-17 23:41 ` Kyle McMartin
2008-12-18 10:23 ` Randolph Chung [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=494A249E.9070405@tausq.org \
--to=randolph@tausq.org \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
/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