linux-kernel - Re: BUG: scheduling while atomic, new libata code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9e4733910612281443t53a1bbd8n97bbb35651cf6929@mail.gmail.com>
Date:	Thu, 28 Dec 2006 17:43:48 -0500
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Arnd Bergmann" <arnd@...db.de>
Cc:	"Randy Dunlap" <randy.dunlap@...cle.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: BUG: scheduling while atomic, new libata code

On 12/28/06, Arnd Bergmann <arnd@...db.de> wrote:
> On Thursday 28 December 2006 03:16, Jon Smirl wrote:
> > BUG: scheduling while atomic: hald-addon-stor/0x20000000/5078
> > [<c02b0289>] __sched_text_start+0x5f9/0xb00
> > [<c024a623>] net_rx_action+0xb3/0x180
> > [<c01210f2>] __do_softirq+0x72/0xe0
> > [<c0105205>] do_IRQ+0x45/0x80
>
> This doesn't seem to be related to libata at all. Like your
> first trace, you call schedule from a softirq context, which
> is always atomic.
> The only place where I can imagine this happening is the
> local_irq_enable() in there, which can be defined in different
> ways.
> Are you running with paravirt_ops, CONFIG_TRACE_IRQFLAGS_SUPPORT
> and/or kernel preemption enabled?

This is set, although I don't recall setting it.
CONFIG_TRACE_IRQFLAGS_SUPPORT=y

# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y

Another odd thing I'm doing is simultaneously using a wired and
wireless net at the same time.

>
>         Arnd <><
>


-- 
Jon Smirl
jonsmirl@...il.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/