linux-kernel - Re: 2.6.18.4: flush_workqueue calls mutex

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: <1165996947.27217.725.camel@laptopd505.fenrus.org>
Date:	Wed, 13 Dec 2006 09:02:27 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	xb <xavier.bru@...l.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.18.4: flush_workqueue calls mutex_lock in interrupt
	environment

On Wed, 2006-12-13 at 08:25 +0100, xb wrote:
> Hi all,
> 
> Running some IO stress tests on a 8*ways IA64 platform, we got:
>      BUG: warning at kernel/mutex.c:132/__mutex_lock_common()  message
> followed by:
>      Unable to handle kernel paging request at virtual address
> 0000000000200200
> oops corresponding to anon_vma_unlink() calling list_del() on a
> poisonned list.
> 
> Having a look to the stack, we see that flush_workqueue() calls
> mutex_lock() with softirqs disabled.

something is wrong here... flush_workqueue() is a sleeping function and
is not allowed to be called in such a context!


-
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/