On Wed, Jul 22, 2015 at 09:52:37PM +0200, Jiri Kosina wrote: > On Wed, 22 Jul 2015, Josh Poimboeuf wrote: > > > Ok, so it sounds like Jiri's suggestion to put the address in the > > attribute won't fly. > > Yeah. Well, there are still alternatives: > > - use proper address in case kptr_restrict is not set > - hash the address otherwise > > That will still maintain the property of being unique and in > !kptr_restrict cases will provide address as a benefit. Hm, but what if kptr_restrict gets changed after we create the kobject? > Removing it altogether is probably a viable option as well, although it's > far more userspace-visible change. Depends on your definition of "userspace-visible", a la: https://en.wikipedia.org/wiki/If_a_tree_falls_in_a_forest :-) -- Josh -- 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
