Re: module: s390: keep mod_arch_specific for livepatch modules

From
Jessica Yu <hidden>
Date
2016-02-04 01:37:59
Also in
linux-s390, lkml
Reply to
Jessica Yu, 2016-02-04
+++ Jessica Yu [03/02/16 20:11 -0500]:
Livepatch needs to utilize the symbol information contained in the
mod_arch_specific struct in order to be able to call the s390
apply_relocate_add() function to apply relocations. Keep a reference to
syminfo if the module is a livepatch module. Remove the redundant vfree()
in module_finalize() since module_arch_freeing_init() (which also frees
those structures) is called in do_init_module(). If the module isn't a
livepatch module, we free the structures in module_arch_freeing_init() as
usual.

Signed-off-by: Jessica Yu <redacted>
---
arch/s390/kernel/module.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
I must note that I have verified that the patchset boots on s390 and
that the sample livepatch module still works ...so that's good, but
not saying much since what we really want is to test the relocation
code. The kpatch build scripts however currently only support x86, so
the next step is for me to port the kpatch scripts to s390 before I
can really test this patchset. This in itself might take a while, so
in the meantime I'd like to just collect another round of comments and
feedback for v4.

Jessica
Thread (27 messages) 27 messages, 6 authors, last reply 2016-02-10
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help