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:	Thu, 12 Feb 2009 01:09:55 -0500 (EST)
From:	Tim Abbott <tabbott@....EDU>
To:	Jon Masters <jonathan@...masters.org>
cc:	Rusty Russell <rusty@...tcorp.com.au>,
	linux-kernel@...r.kernel.org, Jeff Arnold <jbarnold@....edu>,
	Anders Kaseorg <andersk@....edu>
Subject: Re: [PATCH 6/9] Ksplice: Add functions for walking kallsyms
 symbols

On Wed, 11 Feb 2009, Jon Masters wrote:

> Folks,
> 
> Please forgive me not tracking ksplice closely enough - I didn't think
> it required these changes - is there some refactoring going on currently
> or am I mistaken and these patches are now a necessary pre-req.?

Hi Jon,

There are two different versions of the Ksplice kernel module, a 
"standalone" version that works with an unmodified kernel, and the version 
that we've proposed for mainline merge.

One difference between the two versions is that the standalone version has 
implementations of functions such as kallsyms_on_each_symbol in the 
Ksplice core module (i.e. the module containing ksplice.c).

Normally, one would not be able to implement kallsyms_on_each_symbol in a 
module, because it would not have access to necessary symbols such as 
kallsyms_num_syms (an unexported global symbol).  The standalone version 
of Ksplice resolves these symbols through a bootstrapping process.

This bootstrapping technique doesn't make any sense for a Ksplice in 
mainline; these prerequisite patches put functions such as 
kallsyms_on_each_symbol where they belong.

	-Tim Abbott


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ