linux-kernel - Re: [RFC PATCH 0/2] kpatch: dynamic kernel patching

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]

Date:	Mon, 5 May 2014 10:55:37 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Josh Poimboeuf <jpoimboe@...hat.com>
Cc:	Seth Jennings <sjenning@...hat.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>, Jiri Slaby <jslaby@...e.cz>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC PATCH 0/2] kpatch: dynamic kernel patching


* Josh Poimboeuf <jpoimboe@...hat.com> wrote:

> [...]
> 
> kpatch checks the backtraces of all tasks in stop_machine() to 
> ensure that no instances of the old function are running when the 
> new function is applied.  I think the biggest downside of this 
> approach is that stop_machine() has to idle all other CPUs during 
> the patching process, so it inserts a small amount of latency (a few 
> ms on an idle system).

When live patching the kernel, how about achieving an even 'cleaner' 
state for all tasks in the system: to freeze all tasks, as the suspend 
and hibernation code (and kexec) does, via freeze_processes()?

That means no tasks in the system have any real kernel execution 
state, and there's also no problem with long-sleeping tasks, as 
freeze_processes() is supposed to be fast as well.

I.e. go for the most conservative live patching state first, and relax 
it only once the initial model is upstream and is working robustly.

Thanks,

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