linux-kernel - Re: call_rcu from trace

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: <5580C7A7.5040705@plumgrid.com>
Date:	Tue, 16 Jun 2015 18:04:39 -0700
From:	Alexei Starovoitov <ast@...mgrid.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	Daniel Wagner <wagi@...om.org>, paulmck@...ux.vnet.ibm.com,
	Daniel Wagner <daniel.wagner@...-carit.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: call_rcu from trace_preempt

On 6/16/15 5:47 PM, Steven Rostedt wrote:
> Do what I do in tracing. Use a bit (per cpu?) test.
>
> Add the element to the list (that will be a cmpxchg, but I'm not sure
> you can avoid it), then check the bit to see if the irq work is already
> been activated. If not, then activate the irq work and set the bit.
> Then you will not have any more cmpxchg in the fast path.

you mean similar to what rb_wakeups() and friends are doing?
makes sense. starting to study it...

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