On Wed, 22 Jul 2015, Josh Poimboeuf wrote: > > 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? If kptr_restrict == 1, we could just make the directory visible only to the holders of the corresponding capabilities. For kptr_restrict == 2, there is really no good solution indeed. > > 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 > > :-) My past experience suggests that in practice this experiment can be reformulated as "If a tree falls in a forrest, Linus usually notices". :) -- Jiri Kosina SUSE Labs -- 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
