linux-kernel - [PATCH 0/2] introduce kaslr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 27 Apr 2015 16:27:32 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	x86@...nel.org, Borislav Petkov <bp@...en8.de>,
	Kees Cook <keescook@...omium.org>,
	Josh Poimboeuf <jpoimboe@...hat.com>,
	Seth Jennings <sjenning@...hat.com>,
	Vojtech Pavlik <vojtech@...e.cz>
cc:	linux-kernel@...r.kernel.org, live-patching@...r.kernel.org
Subject: [PATCH 0/2] introduce kaslr_offset() and its users

There is already in-kernel code which computes the offset that has been 
used for kASLR -- that's dump_kernel_offset() notifier. As there is now a 
potential second user coming, it seems reasonable to provide a common 
helper that will compute the offset.

- Patch 1/2 introduces kaslr_offset() which computes the kASLR offset, and 
  converts dump_kernel_offset() to make use of it
- Patch 2/2 extends the - currently limited - functionality of 
  livepatching when kASLR has been enabled and is active

----------------------------------------------------------------
Jiri Kosina (2):
      x86: introduce kaslr_offset()
      livepatch: x86: make kASLR logic more accurate

 arch/x86/include/asm/livepatch.h | 1 +
 arch/x86/include/asm/setup.h     | 6 ++++++
 arch/x86/kernel/setup.c          | 2 +-
 kernel/livepatch/core.c          | 5 +++--
 4 files changed, 11 insertions(+), 3 deletions(-)

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/