lkml.org 
[lkml]   [1999]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: access_ok inside kernelspace
    On Tue, 19 Oct 1999, Horst von Brand wrote:
    > I don't understand this. A module is linked into the running kernel, and
    > has access to all of it AFAIU, so I can't see any need for this contortion
    > for modules. Maybe I'm just plain blind today...
    The kernel only has access to symbols which base kernel chose to export
    (kernel/ksyms.c and arch/i386/kernel/i386_ksyms.c). However, you are not
    blind and neither was I - just slightly short-sighted :)

    I forgot about the well-known fact that sys_call_table[] is exported so
    modules should call sys_XXX() functions indirectly via sys_call_table[].
    I even wrote a little module ages ago that is based solely on this simple
    fact.

    Regards,
    Tigran.



    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:54    [W:0.018 / U:1.384 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site