Re: loading a module

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > I wonder how the kernel will know which module to be loaded.
> 
> The kernel doesn't know, it just asks modprobe to do the dirty job.

Anyway. How does the kernel know it should load a module? It sure does
know when device is open (if it has no driver, it composes alias from
the major number (eq. char-major-36) and asks modprobe to load this). But
when a syscall is not installed...
& there's no entry.S entry - the sys_ni_syscall is called which returns an error.
& there is entry in entry.S - but than part of the handling has to be compiled in.

... or is there some way sys_ni_syscall tries to load module? under which alias?

--------------------------------------------------------------------------------
                  				- Jan Hudec `Bulb' <bulb@ucw.cz>
-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.kernelnewbies.org/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux