Re: [PATCH v3 2/2] extable: verify address is read-only

2017-03-23 Thread Kees Cook
On Wed, Mar 22, 2017 at 7:55 PM, Eddie Kovsky wrote: > Provide a mechanism to check if the address of a variable is > const or ro_after_init. It mimics the existing functions that test if an > address is inside the kernel's text section. > > Other functions inside the kernel

Re: [PATCH v3 2/2] extable: verify address is read-only

2017-03-23 Thread Kees Cook
On Wed, Mar 22, 2017 at 7:55 PM, Eddie Kovsky wrote: > Provide a mechanism to check if the address of a variable is > const or ro_after_init. It mimics the existing functions that test if an > address is inside the kernel's text section. > > Other functions inside the kernel could then use this

[PATCH v3 2/2] extable: verify address is read-only

2017-03-22 Thread Eddie Kovsky
Provide a mechanism to check if the address of a variable is const or ro_after_init. It mimics the existing functions that test if an address is inside the kernel's text section. Other functions inside the kernel could then use this capability to verify that their arguments are read-only.

[PATCH v3 2/2] extable: verify address is read-only

2017-03-22 Thread Eddie Kovsky
Provide a mechanism to check if the address of a variable is const or ro_after_init. It mimics the existing functions that test if an address is inside the kernel's text section. Other functions inside the kernel could then use this capability to verify that their arguments are read-only.