linux-kernel - RE: BUG: sleeping function called from invalid context at kernel/fork.c:385

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: <617E1C2C70743745A92448908E030B2A01929C15@scsmsx411.amr.corp.intel.com>
Date:	Wed, 30 May 2007 16:19:11 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"Christoph Lameter" <clameter@....com>
Cc:	"David Chinner" <dgc@....com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"lkml" <linux-kernel@...r.kernel.org>,
	<linux-ia64@...r.kernel.org>, "Sam Ravnborg" <sam@...nborg.org>
Subject: RE: BUG: sleeping function called from invalid context at kernel/fork.c:385

> `.exit.text' referenced in section `.init.text' of drivers/built-in.o: 
> defined in discarded section `.exit.text' of drivers/built-in.o

This one is a fatal error ... the code is trying to call a function
that has been marked __exit in a driver that has been built-in, instead
of as a module.  Since a builtin driver can never be unloaded, the kernel
has thrown away all the __exit routines (at link time).

The error message appears less than helpful in tracking down which
routine in which driver is the problem though.

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