On Fri, 09 Mar 2001, Graham Murray wrote:
>"Mohammad A. Haque" <mhaque@haque.net> writes:
>
>> making a patch means you've modfied the source which you are not allowed
>> to do. The most you can do is report the bug through normal channels
>> (you dont even have priority in reporting bugs since you have the code).
>
>Does making a patch necessarily require modifying the source code?
>Back in my days as a mainframe systems programmer (ICL VME/B), most OS
>patches were made to the binary image, either in the file or to the
>loaded virtual memory image.
Nearly always. The problem is that the patch may make the module bigger/smaller
or relocate variables whose address then changes. All locations that
these are referenced must be modified (either direct address or offset).
Sometimes other modules will get relocated too.
Now when you have relocatable object code distributed there is an alternative:
you recompile the module, and relink the entire kernel. The assumption is
that you have all the object modules...
-- ------------------------------------------------------------------------- Jesse I Pollard, II Email: jesse@cats-chateau.netAny opinions expressed are solely my own. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 15 2001 - 21:00:10 EST