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: <49F12DEA.6070404@redhat.com>
Date:	Thu, 23 Apr 2009 23:11:38 -0400
From:	Masami Hiramatsu <mhiramat@...hat.com>
To:	Tim Abbott <tabbott@....EDU>
CC:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Anders Kaseorg <andersk@....EDU>, Ingo Molnar <mingo@...e.hu>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jeffrey B Arnold <jbarnold@....EDU>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>
Subject: Re: [PATCH 1/5] ftrace: use module notifier for function tracer

Tim Abbott wrote:
> The reason that we want to export text_mutex is that it can be useful for 
> the Ksplice core (still kernel/ksplice.c) to be built as a module.  This 
> is desirable when a different version of the kernel/ksplice.c code is 
> needed in order to apply a particular update (e.g. because there was a bug 
> in Ksplice).

Ah, OK. Certainly, Ksplice can't patch itself. It might be a good reason for
exporting text_mutex.


> I agree that great care should be taken when writing code that patches the 
> kernel's text.  However, I don't think failing to export text_mutex to GPL 
> modules helps ensure that.  In particular, not exporting text_mutex 
> doesn't prevent modules from patching the kernel text.  It just prevents 
> any modules that do so from grabbing the appropriate lock.

What I'm concerned about exporting locking staffs is that may cause
a dead lock. However, we've already exported module_mutex.
I don't think that exporting text_mutex is more considerable than that. :-)

Thank you,

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division

e-mail: mhiramat@...hat.com

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