linux-kernel - Re: [PATCH] x86: export pv_lock

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: <48AD970D.40209@goop.org>
Date:	Thu, 21 Aug 2008 09:25:49 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] x86: export pv_lock_ops non-GPL

Ingo Molnar wrote:
> uhm, why is this even a question? All of this stuff is so deep inside 
> the guts of the kernel ... so nope - if then we want to change the 
> others to _GPL exports as well, just to make sure nobody gets funny 
> ideas.

pv_lock_ops gets accessed by inline functions which get inlined into
modules.  They should never directly access it, but the generated code
will.  _spin_lock() is in exactly the same situation.

    J

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