linux-kernel - Re: live patching design (was: Re: [PATCH 1/3] sched: add sched_task

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1502212144340.2357@pobox.suse.cz>
Date:	Sat, 21 Feb 2015 21:53:33 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Ingo Molnar <mingo@...nel.org>
cc:	Vojtech Pavlik <vojtech@...e.com>,
	Josh Poimboeuf <jpoimboe@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	Seth Jennings <sjenning@...hat.com>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: live patching design (was: Re: [PATCH 1/3] sched: add
 sched_task_call())

To make sure that this thread doesn't conclude in void, here's my take on 
it:

- what's currently alredy there is the simplest-of-simplest methods; it
  allows you to apply context-less patches (such as adding bounds checking 
  to the beginning of syscall, etc), which turns out to cover vast portion 
  of applicable CVEs

- it can always be made more clever; patch author always has to know the 
  version of the kernel he's preparing the patch for anyway (the live 
  patch and the kernel is closely tied together)

- the proposal to force sleeping or CPU-hogging tasks through a defined 
  safe checkpoint using a fake sort-of signal without any other 
  sideeffects might be useful even for kGraft and also for other proposed 
  aproaches. I think we'll try to implement this as an optimization for 
  kGraft and we'll see how (a) fast (b) non-intrusive we would be able to 
  make it. If it turns out to be successful, we can then just reuse it in 
  the upstream solution (whatever that would be)

Thanks,

-- 
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/