Re: livepatch: old_name@old_addr scheme in livepatch sysfs directory

2015-11-02 Thread Jessica Yu
+++ Jiri Kosina [01/11/15 10:07 +0100]: On Sat, 31 Oct 2015, Chris J Arges wrote: Makes sense to me. Is there a reason why the sysfs entries are visible to non-root users? Well, kptr_restrict applies only to values printed using '%pK'. So if the sysfs handler is using other printk() format st

Re: livepatch: old_name@old_addr scheme in livepatch sysfs directory

2015-11-01 Thread Jiri Kosina
On Sat, 31 Oct 2015, Chris J Arges wrote: > Makes sense to me. Is there a reason why the sysfs entries are visible > to non-root users? Well, kptr_restrict applies only to values printed using '%pK'. So if the sysfs handler is using other printk() format string to print the pointer, it'll be le

Re: livepatch: old_name@old_addr scheme in livepatch sysfs directory

2015-10-31 Thread Chris J Arges
On 10/31/2015 08:53 PM, Jessica Yu wrote: > +++ Chris J Arges [30/10/15 22:44 -0500]: >> The following directory structure will allow for cases when the same >> function name exists in a single object. >> /sys/kernel/livepatch/// > > Hi Chris, thanks for the patch. > > I think the last time t

Re: livepatch: old_name@old_addr scheme in livepatch sysfs directory

2015-10-31 Thread Jessica Yu
+++ Chris J Arges [30/10/15 22:44 -0500]: The following directory structure will allow for cases when the same function name exists in a single object. /sys/kernel/livepatch/// Hi Chris, thanks for the patch. I think the last time this issue was discussed, the conclusion was that conca