linux-kernel - Re: [PATCH] module: Introduce MODULE_STATE_COMING

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:	Wed, 2 Apr 2014 08:36:03 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Takao Indoh <indou.takao@...fujitsu.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] module: Introduce MODULE_STATE_COMING_FINAL to avoid
 ftrace warning

On Wed,  2 Apr 2014 16:54:26 +0900
Takao Indoh <indou.takao@...fujitsu.com> wrote:

> This patch adds new module state MODULE_STATE_COMING_FINAL to avoid
> ftrace waring message when loading two modules simultaneously.
> 
> The original patch was written by Steven Rostedt, see below.
> https://lkml.org/lkml/2014/3/24/242
> 


> 
> This patch introduces MODULE_STATE_COMING_FINAL which means that the
> module is ready to be changed to ReadOnly. By this, the modules B is not
> change to RO at (2) because its state is still MODULE_STATE_COMING, so
> this warning message is avoided. Module B is changed to RO in the
> do_init_module() after comes back from notifier.
> 
> Signed-off-by: Takao Indoh <indou.takao@...fujitsu.com>

As I'm the original author, add my:

Signed-off-by: Steven Rostedt <rostedt@...dmis.org>

too.

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