Re: [RFC][PATCH] Prevent overriding of Symbols in the Kernel, avoiding Undefined behaviour

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

 



Ashutosh Naik <[email protected]> wrote:
>
> When a symbol is exported from the kernel, and say, a module would
>  export the same symbol, there currently exists no mechanism to prevent
>  the module from exporting this symbol. The module would still go ahead
>  and export the symbol, the symbol table would now contain two copies
>  of the exported symbol, and hell would break loose.
> 
>  This patch prevents that from happening, by checking the symbol table
>  before relocation for all occurences of the Exported Symbol. If the
>  symbol already exists, we branch out with -ENOEXEC. Currently, this
>  search is sequential.

Do we really need to do this at runtime?  We could check this when building
module depoendencies (for example).  That'll be a 95% solution..
-
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/

[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]
  Powered by Linux