linux-kernel - Re: [PATCH 7/9] rcu: use this_cpu_ptr per-cpu helper instead of per_cpu_ptr(p, raw_smp_processor

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50912593.8050305@gmail.com>
Date:	Wed, 31 Oct 2012 21:20:19 +0800
From:	Shan Wei <shanwei88@...il.com>
To:	paulmck@...ux.vnet.ibm.com
CC:	dipankar@...ibm.com,
	Kernel-Maillist <linux-kernel@...r.kernel.org>,
	cl@...ux-foundation.org
Subject: Re: [PATCH 7/9] rcu:  use this_cpu_ptr per-cpu helper instead of
 per_cpu_ptr(p, raw_smp_processor_id())

Paul E. McKenney said, at 2012/10/31 19:51:
> 
> The first uses smp_processor_id(), which will complain if
> force_quiescent_state() is called with preemption disabled, which it
> sometimes is.
> 
> So what am I missing here?

Hi Paul

this patch is not right for CONFIG_DEBUG_PREEMPT case.
__this_cpu_ptr is ok which do not check for preemption context.


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