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: <20080131211817.GA21210@elte.hu>
Date:	Thu, 31 Jan 2008 22:18:17 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Adrian Bunk <bunk@...nel.org>, tglx@...utronix.de, hpa@...or.com,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: x86: Why have __copy_from_user_ll_nocache* been exported?


* Andrew Morton <akpm@...ux-foundation.org> wrote:

> > A commit that does nothing except for adding two unused 
> > EXPORT_SYMBOL's.
> > 
> > Without any rationale why they should be exported.
> 
> Don't look at me.  This has been sitting in my tree for nearly two 
> years as part of the reiser4 patchset.  It may not even be needed any 
> more.  I guess Ingo went on a fishing expedition and liked the change.

yes, i picked it up from -mm (as can be seen from the SOB line), and i 
agreed with that change regardless of the reiser4 patchset. (which might 
never see the light of upstream acceptance)

there's nothing more annoying than incomplete and inconsistent APIs. I'm 
trying to fix them up everywhere i see, and this is one of those cases. 
Adrian still has not given any rationale about why he wants to see the 
export removed.

	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/