Re: [PATCH 3/3] Assert notifier_block and notifier_call are not in init section

On Tue, 25 Apr 2006, Alan Stern wrote:
> 
> What about loadable modules?  Is their code never loaded into memory that
> used to be part of an init section?

Their code might _physically_ reside in a re-allocation of an init 
section, but will have a virtual address far away (and it would be the 
virtual address that you'd see if you took the address of a function).

		Linus
-
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:
  • Re: [PATCH 3/3] Assert notifier_block and notifier_call are not in init section
    • From: "Randy.Dunlap" <[email protected]>

• References:
  • Re: [PATCH 3/3] Assert notifier_block and notifier_call are not in init section
    • From: Alan Stern <[email protected]>

• Prev by Date: Re: [PATCH 1/2] strstrip API
• Next by Date: Re: [uml-devel] Re: [RFC] PATCH 3/4 - Time virtualization : PTRACE_SYSCALL_MASK
• Previous by thread: Re: [PATCH 3/3] Assert notifier_block and notifier_call are not in init section
• Next by thread: Re: [PATCH 3/3] Assert notifier_block and notifier_call are not in init section
• 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]