linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v6 0/4] ro protection for dynamic data
@ 2017-06-07 12:35 Igor Stoppa
  2017-06-07 12:35 ` [PATCH 1/4] LSM: Convert security_hook_heads into explicit array of struct list_head Igor Stoppa
                   ` (3 more replies)
  0 siblings, 4 replies; 8+ messages in thread
From: Igor Stoppa @ 2017-06-07 12:35 UTC (permalink / raw)
  To: keescook, mhocko, jmorris
  Cc: penguin-kernel, paul, sds, casey, hch, labbott,
	linux-security-module, linux-mm, linux-kernel, kernel-hardening,
	Igor Stoppa

Hi,
please consider for inclusion.

This patchset introduces the possibility of protecting memory that has
been allocated dynamically.

The memory is managed in pools: when a pool is made R/O, all the memory
that is part of it, will become R/O.

A R/O pool can be destroyed to recover its memory, but it cannot be
turned back into R/W mode.

This is intentional. This feature is meant for data that doesn't need
further modifications, after initialization.

An example is provided, showing how to turn into a boot-time option the
writable state of the security hooks.
Prior to this patch, it was a compile-time option.

This is made possible, thanks to Tetsuo Handa's rework of the hooks
structure (included in the patchset).

Changes since the v5 version:
- use unsigned long for  __PMALLOC_ALIGNED alignment
- fixed a regression where size in bytes was used instead of size in words
- tightened the update of the pools list during removal, by doing
  earlier the decrement of the atomic counter

The only question still open is if there should be a possibility for
unprotecting a memory pool in other cases than destruction.

The only cases found for this topic are:
- protecting the LSM header structure between creation and insertion of a
  security module that was not built as part of the kernel
  (but the module can protect the headers after it has loaded)

- unloading SELinux from RedHat, if the system has booted, but no policy
  has been loaded yet - this feature is going away, according to Casey.


Igor Stoppa (3):
  Protectable Memory Allocator
  Protectable Memory Allocator - Debug interface
  Make LSM Writable Hooks a command line option

Tetsuo Handa (1):
  LSM: Convert security_hook_heads into explicit array of struct
    list_head

 include/linux/lsm_hooks.h      | 412 ++++++++++++++++++++---------------------
 include/linux/page-flags.h     |   2 +
 include/linux/pmalloc.h        |  20 ++
 include/trace/events/mmflags.h |   1 +
 init/main.c                    |   2 +
 mm/Kconfig                     |  11 ++
 mm/Makefile                    |   1 +
 mm/pmalloc.c                   | 339 +++++++++++++++++++++++++++++++++
 mm/usercopy.c                  |  24 ++-
 security/security.c            |  49 +++--
 10 files changed, 631 insertions(+), 230 deletions(-)
 create mode 100644 include/linux/pmalloc.h
 create mode 100644 mm/pmalloc.c

-- 
2.9.3

^ permalink raw reply	[flat|nested] 8+ messages in thread
* [RFC v5 PATCH 0/4] NOT FOR MERGE - ro protection for dynamic data
@ 2017-06-06 18:24 Igor Stoppa
  2017-06-06 18:24 ` [PATCH 2/4] Protectable Memory Allocator Igor Stoppa
  0 siblings, 1 reply; 8+ messages in thread
From: Igor Stoppa @ 2017-06-06 18:24 UTC (permalink / raw)
  To: keescook, mhocko, jmorris
  Cc: penguin-kernel, paul, sds, casey, hch, labbott,
	linux-security-module, linux-mm, linux-kernel, kernel-hardening,
	Igor Stoppa

This patchset introduces the possibility of protecting memory that has
been allocated dynamically.

The memory is managed in pools: when a pool is made R/O, all the memory
that is part of it, will become R/O.

A R/O pool can be destroyed to recover its memory, but it cannot be
turned back into R/W mode.

This is intentional. This feature is meant for data that doesn't need
further modifications, after initialization.

An example is provided, showing how to turn into a boot-time option the
writable state of the security hooks.
Prior to this patch, it was a compile-time option.

This is made possible, thanks to Tetsuo Handa's rework of the hooks
structure (included in the patchset).

Since the previous version, I have applied fixes for all the issues
discovered that had a clear resolution:

- %p -> pK
- make the feature depend on ARCH_HAS_SET_MEMORY
- fix the range of the page scanning for hardened user copy
- fixed pointer checking for NULL dereferencing


And a couple of issues I found myself:
- return NULL in case someone asks memory from a locked pool
- turn the "protected" flag into atomic type


Still open (at least I didn't get the impression there was a closure):
- need for specific __PMALLOC_ALIGNED ?
- is it really needed to unprotect a pool?
  can't it wait for the implementation of write-seldom?


Igor Stoppa (3):
  Protectable Memory Allocator
  Protectable Memory Allocator - Debug interface
  Make LSM Writable Hooks a command line option

Tetsuo Handa (1):
  LSM: Convert security_hook_heads into explicit array of struct
    list_head

 include/linux/lsm_hooks.h      | 412 ++++++++++++++++++++---------------------
 include/linux/page-flags.h     |   2 +
 include/linux/pmalloc.h        |  20 ++
 include/trace/events/mmflags.h |   1 +
 init/main.c                    |   2 +
 mm/Kconfig                     |  11 ++
 mm/Makefile                    |   1 +
 mm/pmalloc.c                   | 340 ++++++++++++++++++++++++++++++++++
 mm/usercopy.c                  |  24 ++-
 security/security.c            |  49 +++--
 10 files changed, 632 insertions(+), 230 deletions(-)
 create mode 100644 include/linux/pmalloc.h
 create mode 100644 mm/pmalloc.c

-- 
2.9.3

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2017-06-19  7:13 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-07 12:35 [PATCH v6 0/4] ro protection for dynamic data Igor Stoppa
2017-06-07 12:35 ` [PATCH 1/4] LSM: Convert security_hook_heads into explicit array of struct list_head Igor Stoppa
2017-06-07 12:35 ` [PATCH 2/4] Protectable Memory Allocator Igor Stoppa
2017-06-09 18:56   ` Laura Abbott
2017-06-19  7:12     ` Igor Stoppa
2017-06-07 12:35 ` [PATCH 3/4] Protectable Memory Allocator - Debug interface Igor Stoppa
2017-06-07 12:35 ` [PATCH 4/4] Make LSM Writable Hooks a command line option Igor Stoppa
  -- strict thread matches above, loose matches on Subject: below --
2017-06-06 18:24 [RFC v5 PATCH 0/4] NOT FOR MERGE - ro protection for dynamic data Igor Stoppa
2017-06-06 18:24 ` [PATCH 2/4] Protectable Memory Allocator Igor Stoppa

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).