linux-kernel - Re: [PATCH] rcu: don't call rcu_preempt_note_context_switch() in rcu_check

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: <4BB44A15.60306@cn.fujitsu.com>
Date:	Thu, 01 Apr 2010 15:24:05 +0800
From:	Lai Jiangshan <laijs@...fujitsu.com>
To:	paulmck@...ux.vnet.ibm.com
CC:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rcu: don't call rcu_preempt_note_context_switch() in
 rcu_check_callbacks()

Paul E. McKenney wrote:
> Possibly by moving the clearing of RCU_READ_UNLOCK_NEED_QS to
> rcu_preempt_check_callbacks() 

current rcu_preempt_check_callbacks() already has code to
clear RCU_READ_UNLOCK_NEED_QS.

> -- or to rcu_preempt_qs().  The latter is in
> some sense cleaner, but higher overhead and probably unnecessary.  Hmmm...
> Alternatively, require that all callers to rcu_preempt_qs() disable
> irqs.  This affects only one callsite, which has a local_irq_disable()
> immediately following anyway.  ;-)
> 
> 							Thanx, Paul

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