linux-kernel - Re: [PATCH] Linux Kernel Markers

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:	Tue, 19 Sep 2006 09:52:55 -0700
From:	Martin Bligh <mbligh@...gle.com>
To:	"Frank Ch. Eigler" <fche@...hat.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Paul Mundt <lethal@...ux-sh.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jes Sorensen <jes@....com>, Andrew Morton <akpm@...l.org>,
	Tom Zanussi <zanussi@...ibm.com>,
	Richard J Moore <richardj_moore@...ibm.com>,
	Michel Dagenais <michel.dagenais@...ymtl.ca>,
	Christoph Hellwig <hch@...radead.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	William Cohen <wcohen@...hat.com>, ltt-dev@...fik.org,
	systemtap@...rces.redhat.com, Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] Linux Kernel Markers

Frank Ch. Eigler wrote:
> Martin Bligh <mbligh@...gle.com> writes:
> 
> 
>>[...]  "compiled anew from original sources after deployment" seems
>>the most practical to do to me.  From second hand info on using
>>systemtap, you seem to need the same compiler and source tree to
>>work from anyway [...]
> 
> 
> Not quite.  Systemtap does not look at sources, only object code and
> its embedded debugging information.  (How many distributions keep
> around compilable source trees?)

???? Boggle. Any distro that cannot find the source code for it's kernel
deserves a swift kick to the head, plus a red hot poker somewhere else.

>>[...] It seems like all we'd need to do is "list all references to
>>function, freeze kernel, update all references, continue", [...]
> 
> One additional problem are external references made *by* the function.
> Those too would all have to be relocated to the live data.

Not sure what you mean ... could you give a quick example?

> Live code patching is theoretically useful for all kinds of things,
> but I've never heard it described as relatively simple before! :-)

well, on a whole-function basis, it seems somewhat simpler.

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