linux-kernel - Re: spin_lock after get_cpu

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]

Date:	Sun, 16 Mar 2008 11:12:45 +0100
From:	Johannes Weiner <hannes@...urebad.de>
To:	"Peter Teoh" <htmldeveloper@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: spin_lock after get_cpu_var()

Hi Peter,

"Peter Teoh" <htmldeveloper@...il.com> writes:

> I find it quite puzzling (no where else in kernel source is this
> found) that you would want to apply spin_lock() after get_cpu_var().
> The fddef is already percpu, so there is no need to lock it, right?
>
> I submitted this patch before, but got no response, just trying my
> luck this time :-).

http://lkml.org/lkml/2008/3/14/208

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