linux-kernel - Re: x86: Why have __copy_from_user_ll

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: <20080201095034.GA29960@elte.hu>
Date:	Fri, 1 Feb 2008 10:50:34 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Andrew Morton <akpm@...l.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: x86: Why have __copy_from_user_ll_nocache* been exported?


* Ingo Molnar <mingo@...e.hu> wrote:

> > And that from a person who on the other hand wants to introduce (and 
> > tries to force on other people) deprecation periods for unused 
> > EXPORT_SYMBOL's.
> 
> why does this bother you? The API makes total sense. This is a 
> completely sensible API (with a full implementation) to use 
> non-temporal copies. I mean, if this was some legacy API that nobody 
> uses anymore i'd agree, but this is about the ability to access 
> user-space memory via SSE2+ non-temporal stores.

Adrian, you have still not answered the (obvious) question: why do such 
currently-unused exports bother you?

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