All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tycho Andersen <tycho@docker.com>
To: linux-mm@kvack.org
Cc: Juerg Haefliger <juergh@gmail.com>,
	kernel-hardening@lists.openwall.com,
	Tycho Andersen <tycho@docker.com>
Subject: [kernel-hardening] [RFC v4 0/3] Add support for eXclusive Page Frame Ownership
Date: Wed,  7 Jun 2017 15:16:50 -0600	[thread overview]
Message-ID: <20170607211653.14536-1-tycho@docker.com> (raw)

Hi all,

I have talked with Juerg about picking up the torch for XPFO [1], and have been
playing around with the set for a bit. I've fixed one memory corruption issue
since v3, and also tried and failed at integrating hugepages support. The code
in patch 3 seems to split up the page and apply the right protections, but
somehow the lkdtm test read succeeds and no fault is generated, and I don't
understand why.

[1]: https://lkml.org/lkml/2016/11/4/245

Thoughts welcome,

Tycho

Juerg Haefliger (2):
  mm, x86: Add support for eXclusive Page Frame Ownership (XPFO)
  lkdtm: Add tests for XPFO

Tycho Andersen (1):
  xpfo: add support for hugepages

 Documentation/admin-guide/kernel-parameters.txt |   2 +
 arch/x86/Kconfig                                |   1 +
 arch/x86/include/asm/pgtable.h                  |  22 +++
 arch/x86/mm/Makefile                            |   1 +
 arch/x86/mm/pageattr.c                          |  21 +--
 arch/x86/mm/xpfo.c                              |  82 +++++++++
 drivers/misc/Makefile                           |   1 +
 drivers/misc/lkdtm.h                            |   3 +
 drivers/misc/lkdtm_core.c                       |   1 +
 drivers/misc/lkdtm_xpfo.c                       | 105 ++++++++++++
 include/linux/highmem.h                         |  15 +-
 include/linux/xpfo.h                            |  38 +++++
 mm/Makefile                                     |   1 +
 mm/page_alloc.c                                 |   2 +
 mm/page_ext.c                                   |   4 +
 mm/xpfo.c                                       | 210 ++++++++++++++++++++++++
 security/Kconfig                                |  19 +++
 17 files changed, 508 insertions(+), 20 deletions(-)
 create mode 100644 arch/x86/mm/xpfo.c
 create mode 100644 drivers/misc/lkdtm_xpfo.c
 create mode 100644 include/linux/xpfo.h
 create mode 100644 mm/xpfo.c

-- 
2.11.0

WARNING: multiple messages have this Message-ID (diff)
From: Tycho Andersen <tycho@docker.com>
To: linux-mm@kvack.org
Cc: Juerg Haefliger <juergh@gmail.com>,
	kernel-hardening@lists.openwall.com,
	Tycho Andersen <tycho@docker.com>
Subject: [RFC v4 0/3] Add support for eXclusive Page Frame Ownership
Date: Wed,  7 Jun 2017 15:16:50 -0600	[thread overview]
Message-ID: <20170607211653.14536-1-tycho@docker.com> (raw)

Hi all,

I have talked with Juerg about picking up the torch for XPFO [1], and have been
playing around with the set for a bit. I've fixed one memory corruption issue
since v3, and also tried and failed at integrating hugepages support. The code
in patch 3 seems to split up the page and apply the right protections, but
somehow the lkdtm test read succeeds and no fault is generated, and I don't
understand why.

[1]: https://lkml.org/lkml/2016/11/4/245

Thoughts welcome,

Tycho

Juerg Haefliger (2):
  mm, x86: Add support for eXclusive Page Frame Ownership (XPFO)
  lkdtm: Add tests for XPFO

Tycho Andersen (1):
  xpfo: add support for hugepages

 Documentation/admin-guide/kernel-parameters.txt |   2 +
 arch/x86/Kconfig                                |   1 +
 arch/x86/include/asm/pgtable.h                  |  22 +++
 arch/x86/mm/Makefile                            |   1 +
 arch/x86/mm/pageattr.c                          |  21 +--
 arch/x86/mm/xpfo.c                              |  82 +++++++++
 drivers/misc/Makefile                           |   1 +
 drivers/misc/lkdtm.h                            |   3 +
 drivers/misc/lkdtm_core.c                       |   1 +
 drivers/misc/lkdtm_xpfo.c                       | 105 ++++++++++++
 include/linux/highmem.h                         |  15 +-
 include/linux/xpfo.h                            |  38 +++++
 mm/Makefile                                     |   1 +
 mm/page_alloc.c                                 |   2 +
 mm/page_ext.c                                   |   4 +
 mm/xpfo.c                                       | 210 ++++++++++++++++++++++++
 security/Kconfig                                |  19 +++
 17 files changed, 508 insertions(+), 20 deletions(-)
 create mode 100644 arch/x86/mm/xpfo.c
 create mode 100644 drivers/misc/lkdtm_xpfo.c
 create mode 100644 include/linux/xpfo.h
 create mode 100644 mm/xpfo.c

-- 
2.11.0

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2017-06-07 21:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 21:16 Tycho Andersen [this message]
2017-06-07 21:16 ` [RFC v4 0/3] Add support for eXclusive Page Frame Ownership Tycho Andersen
2017-06-07 21:16 ` [kernel-hardening] [RFC v4 1/3] mm, x86: Add support for eXclusive Page Frame Ownership (XPFO) Tycho Andersen
2017-06-07 21:16   ` Tycho Andersen
2017-06-07 21:16 ` [kernel-hardening] [RFC v4 2/3] lkdtm: Add tests for XPFO Tycho Andersen
2017-06-07 21:16   ` Tycho Andersen
2017-06-07 21:16 ` [kernel-hardening] [RFC v4 3/3] xpfo: add support for hugepages Tycho Andersen
2017-06-07 21:16   ` Tycho Andersen
2017-06-10  0:23   ` [kernel-hardening] " Laura Abbott
2017-06-10  0:23     ` Laura Abbott
2017-06-12 14:31     ` [kernel-hardening] " Tycho Andersen
2017-06-12 14:31       ` Tycho Andersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170607211653.14536-1-tycho@docker.com \
    --to=tycho@docker.com \
    --cc=juergh@gmail.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.