> Good catch. Let me add a disclaimer here and state that this example is > definitely contrived as I was trying to minimize its size. Applying > shadow variables to a more real life use case would drag in a bunch of > "changed" function dependencies. I didn't want to work around those > with a pile of kallsyms workarounds. It did lead you to ask an > interesting question though: You can always create a completely artificial sample based on a real life use case. I mean, you can create a module with functions and data structures you need and then patch one of those functions. You control everything and you can limit dependencies and kallsyms workarounds (or avoid them completely). Miroslav -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
