Re: BUG: sleeping function called from invalid context at kernel/fork.c:385

On Thu, May 31, 2007 at 11:20:27AM -0400, Prarit Bhargava wrote:
> 
> Something is borken in modpost because I found a bug in the loopback 
> code which is a _REAL_ bug.

Here is the result for an i386 allmodconfig build:
WARNING: arch/i386/kernel/built-in.o(.init.text+0x3966): Section mismatch: reference to .exit.text: (between 'microcode_init' and 'parse_maxcpus')
WARNING: arch/i386/kernel/built-in.o(.init.text+0x3992): Section mismatch: reference to .exit.text: (between 'microcode_init' and 'parse_maxcpus')
  Building modules, stage 2.
Kernel: arch/i386/boot/bzImage is ready  (#4)
  MODPOST 2100 modules
WARNING: drivers/acpi/asus_acpi.o(.init.text+0xb7): Section mismatch: reference to .exit.text: (after 'init_module')
WARNING: drivers/acpi/toshiba_acpi.o(.init.text+0x13a): Section mismatch: reference to .exit.text: (after 'init_module')
WARNING: drivers/block/loop.o(.init.text+0x6b): Section mismatch: reference to .exit.text: (after 'init_module')
WARNING: drivers/isdn/hardware/eicon/divadidd.o(.init.text+0xc4): Section mismatch: reference to .exit.text: (between 'init_module' and 'diddfunc_init')
WARNING: drivers/isdn/hardware/eicon/divas.o(.init.text+0xf4): Section mismatch: reference to .exit.text:divasfunc_exit (between 'init_module' and 'divasfunc_init')
WARNING: drivers/isdn/hardware/eicon/divas.o(.init.text+0x10d): Section mismatch: reference to .exit.text:divasfunc_exit (between 'init_module' and 'divasfunc_init')
WARNING: drivers/isdn/hardware/eicon/divas.o(.init.text+0x148): Section mismatch: reference to .exit.text:divasfunc_exit (between 'init_module' and 'divasfunc_init')
WARNING: drivers/kvm/kvm-intel.o(.init.text+0xbd): Section mismatch: reference to .exit.text: (between 'hardware_setup' and 'vmx_disabled_by_bios')
WARNING: drivers/net/hp100.o(.init.text+0x26a): Section mismatch: reference to .exit.text: (after 'init_module')

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • [PATCH] microcode: fix section mismatch warning
    • From: Sam Ravnborg <[email protected]>
  • [PATCH] isdn: fix section mismatch warnings
    • From: Sam Ravnborg <[email protected]>
  • [PATCH] acpi: fix section mismatch warning in asus_acpi.o
    • From: Sam Ravnborg <[email protected]>
  • [PATCH] kvm: fix section mismatch warning in kvm-intel.o
    • From: Sam Ravnborg <[email protected]>
  • [PATCH] net/hp100: fix section mismatch warning
    • From: Sam Ravnborg <[email protected]>

• References:
  • RE: BUG: sleeping function called from invalid context at kernel/fork.c:385
    • From: "Luck, Tony" <[email protected]>
  • RE: BUG: sleeping function called from invalid context at kernel/fork.c:385
    • From: Christoph Lameter <[email protected]>
  • Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
    • From: Prarit Bhargava <[email protected]>

• Prev by Date: Re: [PATCH] x86_64 irq: check remote IRR bit before migrating level triggered irq (v3)
• Next by Date: Re: [PATCH] x86_64 irq: check remote IRR bit before migrating level triggered irq (v2)
• Previous by thread: Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
• Next by thread: [PATCH] net/hp100: fix section mismatch warning
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]