linux-kernel - Re: [PATCH] tracing - enable records during the module load

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:	Sat, 10 Oct 2009 11:26:41 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	jolsa@...hat.com
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing - enable records during the module load

On Sat, 2009-10-10 at 16:00 +0200, jolsa@...hat.com wrote:
> I was debuging some module using "function" and "function_graph" tracers
> and noticed, that if you load module after you enabled tracing, the module's
> hooks will convert only to NOP instructions.

Yeah, I knew when I wrote this that new modules loaded during tracing
would just be initialized as nops, and not become part of that trace.
They will become part of later traces if the function tracing is stopped
and started again.

Actually, I took that as a safety feature, since most bad things can
happen when modules load and unload. But, I think your patch is still
safe. I'll apply it, play with it a bit, then queue it up for 2.6.33.

Thanks,

-- Steve

> 
> The attached patch enables modules' hooks if there's function
> trace allready on, thus allowing to trace module functions.

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