Re: [PATCH 4/7] Protectable Memory

2018-03-12 Thread Igor Stoppa
On 12/03/18 21:13, Matthew Wilcox wrote: > On Wed, Feb 28, 2018 at 10:06:17PM +0200, Igor Stoppa wrote: >> struct gen_pool *pmalloc_create_pool(const char *name, >> int min_alloc_order); >> int is_pmalloc_object(const void *ptr, const unsigned long n); >> boo

Re: [PATCH 4/7] Protectable Memory

2018-03-12 Thread Matthew Wilcox
On Wed, Feb 28, 2018 at 10:06:17PM +0200, Igor Stoppa wrote: > struct gen_pool *pmalloc_create_pool(const char *name, >int min_alloc_order); > int is_pmalloc_object(const void *ptr, const unsigned long n); > bool pmalloc_prealloc(struct gen_pool *pool, size_t

Re: [PATCH 4/7] Protectable Memory

2018-03-07 Thread Igor Stoppa
On 06/03/18 05:59, J Freyensee wrote: [...] >> +config PROTECTABLE_MEMORY >> +bool >> +depends on MMU > > > Curious, would you also want to depend on "SECURITY" as well, as this is > being advertised as a compliment to __read_only_after_init, per the file > header comments, as I'm ass

Re: [PATCH 4/7] Protectable Memory

2018-03-05 Thread J Freyensee
snip . . . + +config PROTECTABLE_MEMORY +bool +depends on MMU Curious, would you also want to depend on "SECURITY" as well, as this is being advertised as a compliment to __read_only_after_init, per the file header comments, as I'm assuming ro_after_init would be disabled if the SE

[PATCH 4/7] Protectable Memory

2018-02-28 Thread Igor Stoppa
The MMU available in many systems running Linux can often provide R/O protection to the memory pages it handles. However, the MMU-based protection works efficiently only when said pages contain exclusively data that will not need further modifications. Statically allocated variables can be segreg

Re: [PATCH 4/7] Protectable Memory

2018-02-26 Thread J Freyensee
inlined responses. On 2/26/18 6:28 AM, Igor Stoppa wrote: On 24/02/18 02:10, J Freyensee wrote: On 2/23/18 6:48 AM, Igor Stoppa wrote: [...] +struct gen_pool *pmalloc_create_pool(const char *name, +int min_alloc_order); Same comments as earlier.  If

Re: [PATCH 4/7] Protectable Memory

2018-02-26 Thread Igor Stoppa
On 24/02/18 02:10, J Freyensee wrote: > On 2/23/18 6:48 AM, Igor Stoppa wrote: [...] >> +struct gen_pool *pmalloc_create_pool(const char *name, >> + int min_alloc_order); > > Same comments as earlier.  If this is new API with new code being > introduced int

Re: [PATCH 4/7] Protectable Memory

2018-02-24 Thread kbuild test robot
Hi Igor, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2] [cannot apply to next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH 4/7] Protectable Memory

2018-02-23 Thread J Freyensee
On 2/23/18 6:48 AM, Igor Stoppa wrote: The MMU available in many systems running Linux can often provide R/O protection to the memory pages it handles. However, the MMU-based protection works efficiently only when said pages contain exclusively data that will not need further modifications. St

[PATCH 4/7] Protectable Memory

2018-02-23 Thread Igor Stoppa
The MMU available in many systems running Linux can often provide R/O protection to the memory pages it handles. However, the MMU-based protection works efficiently only when said pages contain exclusively data that will not need further modifications. Statically allocated variables can be segreg