linux-kernel - Re: [PATCH] export softirq_to

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: <49FB58F7.8080109@redhat.com>
Date:	Fri, 01 May 2009 13:17:59 -0700
From:	Josh Stone <jistone@...hat.com>
To:	Christoph Hellwig <hch@...radead.org>
CC:	Jason Baron <jbaron@...hat.com>, mingo@...e.hu,
	rostedt@...dmis.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] export softirq_to_name symbol

On 05/01/2009 01:10 PM, Christoph Hellwig wrote:
> On Fri, May 01, 2009 at 01:07:34PM -0700, Josh Stone wrote:
>> I'm adding SystemTap support for the format strings in the TRACE_EVENT
>> macros.  The softirq's TP_fast_assign uses softirq_to_name, and so that
>> array is needed to prepare the softirq's trace string.
>>
>> So, there's no explicit reference to the symbol in SystemTap -- it's
>> just indirectly referenced by the tracepoint declaration.
> 
> TP_fast_assign should only be called by core code, it's the piece that
> copies the trace into the ring buffer.  If systemtap copies events into
> the ring buffer from modular code something is deeply wrong in it's
> design.

More precisely, it's the piece of code that copies the trace into an
__entry pointer.  In my case, __entry has nothing to do with the ring
buffer.

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