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] [day] [month] [year] [list]
Message-ID: <20130906084104.2c1e8774@gandalf.local.home>
Date:	Fri, 6 Sep 2013 08:41:04 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Tom Zanussi <tom.zanussi@...ux.intel.com>,
	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH v8 01/10] tracing: Add support for SOFT_DISABLE to
 syscall events

On Fri, 06 Sep 2013 21:22:15 +0900
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:

> 
> And AFAICS, the tracepoint (on which the syscall tracer based)
> call-site uses rcu_read_lock_sched_notrace() instead of rcu_read_lock(),
> in that case, I think we should use synchronize_sched(). is that wrong?
> 

Ah, no, you are correct.  I was thinking that the tracepoints used
rcu_read_lock(), but looking at the code, it's rcu_read_lock_sched().
Thus a synchronize_sched() *is* required.

Thanks, and please ignore my other comments about using
"synchronize_rcu()".

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ