Skip to contentSkip to conversation

New: Exported functions and variables should not be reachable by the outside of the module until module_init finishes

Bugme-new Andrew Morton 1 participant 1 message Aug 29, 2007 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]/

#1 lore raw
Quoted 21 lines · On Wed, 29 Aug 2007 11:33:06 -0700 (PDT) [email protected] wrote:

http://bugzilla.kernel.org/show_bug.cgi?id=8957

Summary: Exported functions and variables should not be reachable
by the outside of the module until module_init finishes
Product: Other
Version: 2.5
KernelVersion: 2.6.23-rc4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Modules
AssignedTo: [email protected]
ReportedBy: [email protected]

Problem Description: a module's exported functions can be called before before they are properly initialized by the module_init function.

Quoted 8 lines

Steps to reproduce: write a module that exports functions that require initialization by the module_init function to work correctly.

E.g. spin lock variables are no longer allowed to be initialized by C initializers of the module but only by spin_lock_init that can be called by the module_init function. If an exported function calls spin_lock before it is initialized, it deadlocks.

ooh, nice bug ;)