On Thu, 2008-01-24 at 07:47 -0500, Mathieu Desnoyers wrote: > There seems to be good arguments for markers to support proprierary modules. > So > I am throwing this one-liner in and let's see how people react. It only makes > sure that a module that has been "forced" to be loaded won't have its markers > used. It is important to leave this check to make sure the kernel does not > crash > by expecting the markers part of the struct module by mistake in the case > there > is an incorrect checksum. > > It applies fine on 2.6.24-rc8-git3.
I think this should go in. Signed-off-by: Jon Masters <[EMAIL PROTECTED]> Jon. P.S. wondering out loud to myself, I finally realized the reason we need a leaf struct_module function in kernel/module.c. We don't necessarily have anything else checking for changes to struct module on module load without this, and we have an embedded struct module in each module that we memory map as we load the module. I did wonder what was protecting us from that (especially forced loads). But Rusty does think of everything. -- 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/
