lkml.org 
[lkml]   [2008]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 3/5] Module: check to see if we have a built in module with the same name

    On Jan 27 2008 15:38, Greg Kroah-Hartman wrote:
    >Subject: [PATCH 3/5] Module: check to see if we have a built in module with the
    > same name
    >
    >When trying to load a module with the same name as a built-in one, a
    >scary kobject backtrace comes up. Prevent that from checking for this
    >condition and warning the user as to what exactly is going on.

    Should not external modules with internal names be rejected at modprobe
    time? Otherwise I'd wonder how you want to deal with /sys/modules/XXX if
    both modules export some module_param()s.

    It's just that if I happen to load vt.ko that the existing
    /sys/modules/vt (from in-kernel vt.o) does not get overwritten by new
    dentries that vt.ko will spawn. Something like /sys/modules/vt.1 perhaps
    for /the new module with same name?


    \
     
     \ /
      Last update: 2008-01-29 00:57    [W:0.019 / U:0.636 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site