[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070824082725.GA2203@ff.dom.local>
Date: Fri, 24 Aug 2007 10:27:25 +0200
From: Jarek Poplawski <jarkao2@...pl>
To: Mariusz Kozlowski <m.kozlowski@...land.pl>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: 2.6.23-rc2-mm1: irq lock inversion dependency detected
On 10-08-2007 09:06, Mariusz Kozlowski wrote:
> Hello,
>
> And the winner of today is ...
>
>
>
> =========================================================
> [ INFO: possible irq lock inversion dependency detected ]
> 2.6.23-rc2-mm1 #7
> ---------------------------------------------------------
> runscript.sh/5843 just changed the state of lock:
> (_xmit_ETHER){-+..}, at: [<c03cbe79>] dev_watchdog+0x17/0xcc
> but this lock took another, soft-irq-unsafe lock in the past:
> (&tp->lock){--..}
>
> and interrupts could create inverse lock ordering between them.
...
> Really no idea who to CC here ;)
IMHO, this should be fixed by last changes to free_irq & request_irq.
(Seems to be possible only with CONFIG_DEBUG_SHIRQ?) Otherwise I can
be CC-ed - my pleasure!
Cheers,
Jarek P.
-
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/
Powered by blists - more mailing lists