| commit | d348ad57fd65b0a59bbca97b5a963b359743a72f | |
| author | Nelson Elhage <nelhage@ksplice.com> | |
| Tue, 11 Aug 2009 21:33:52 +0000 (11 17:33 -0400) | ||
| committer | Anders Kaseorg <andersk@ksplice.com> | |
| Fri, 21 Aug 2009 21:30:38 +0000 (21 17:30 -0400) | ||
| tree | d6a12ebf8f01f4dc1ef3354c3d648490e0c4f1d9 | treesnapshot (tar.gz zip) |
| parent | a90c049a1b637b3b0e0821f1f42473dc304d7813 | commitdiff |
Implement a ksplice_match_data_early option.
If a patch's new code references data (for instance a string) that was
present in the old code, but only pointed to from a '.data' section,
Ksplice will fail to run-pre match the update, since we do not use
relocations derived from .data sections when relocating the new code.
To work around this problem, add support for an option that indicates
that the kernel module should run-pre match a given .data object
before trying to relocate the new code, instead of only doing so
afterwards, as an additional sanity check (which is the default
behavior).
Signed-off-by: Nelson Elhage <nelhage@ksplice.com>
If a patch's new code references data (for instance a string) that was
present in the old code, but only pointed to from a '.data' section,
Ksplice will fail to run-pre match the update, since we do not use
relocations derived from .data sections when relocating the new code.
To work around this problem, add support for an option that indicates
that the kernel module should run-pre match a given .data object
before trying to relocate the new code, instead of only doing so
afterwards, as an additional sanity check (which is the default
behavior).
Signed-off-by: Nelson Elhage <nelhage@ksplice.com>