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

> Hmmm - I wonder if my tree is screwed up in some weird way. I'm seeing link
> warnings as well:
>
> WARNING: init/built-in.o - Section mismatch: reference to .init.data: from .sdata after 'root_mountflags' (at offset 0x38)

I thought that I'd got the section mis-match warnings down to
just one (and that was in ACPI code, so I sent a patch to Len
for it).

Are you building from defconfig, or one of the standard ones? Changing
config options always has the possibility of unearthing new spots
where there are conflicts between __init, __cpuinit and __devinit.

But I've had other complaints that these Section mismatch warnings
are still showing up in kernels built from the "standard" config
files (arch/ia64/configs/*) ... which I'm not seeing.  So I'm more
than a little confused about this.

These errors are unlikely to be related to the strace bug that
you've reported.  I'll try to pound on this some more when I'm
back on the same continent as my test machines.

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