linux-kernel - Re: [PATCH] x86: Enable fast 32-bit put_user_64 for copy_to

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: <20150416074048.GC6193@nuc-i3427.alporthouse.com>
Date:	Thu, 16 Apr 2015 08:40:48 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	intel-gfx@...ts.freedesktop.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Enable fast 32-bit put_user_64 for copy_to_user

On Thu, Apr 16, 2015 at 09:28:02AM +0200, Ingo Molnar wrote:
> 
> * Chris Wilson <chris@...is-wilson.co.uk> wrote:
> 
> > For fixed sized copies, copy_to_user() will utilize __put_user_size
> > fastpaths. However, it is missing the translation for 64bit copies on
> > x86/32. Testing on a Pinetrail Atom, the 64 bit put_user fastpath is
> > substantially faster than the generic copy_to_user() fallback.
> > 
> > Cc: Thomas Gleixner <tglx@...utronix.de>
> > Cc: Ingo Molnar <mingo@...hat.com>
> > Cc: "H. Peter Anvin" <hpa@...or.com>
> > Cc: x86@...nel.org
> > CC: linux-kernel@...r.kernel.org
> 
> The patch makes sense, but your Signed-off-by line is missing.

Sorry, totally forgot that when rewriting the changelog.
Signed-off-by: Chris Wilson <chris@...is-wilson.co.uk>
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
--
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/