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

On Tue, 25 Apr 2006, Linus Torvalds wrote:

> > 2) Unrelated to this patch: If the _code_ section is never reallocated
> > or reused, what is the purpose of putting _code_ in the init section ?
> > Only to make sure that the init calls are called in order ?
> 
> No, the code section is re-used, it's just never re-used for any other 
> code (since we don't generate code on the fly). So if you pass in a 
> function pointer, you know that if it's in the init section, it means that 
> init-code that was discarded.

What about loadable modules?  Is their code never loaded into memory that
used to be part of an init section?

Alan Stern

-
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: Linus Torvalds <[email protected]>

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

• Prev by Date: Telling the kernel that keys need soft release?
• Next by Date: Re: Compiling C++ modules
• 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]