public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: monstr@monstr.eu
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	John Williams <john.williams@petalogix.com>
Subject: Re: generic uaccess.h
Date: Fri, 24 Jul 2009 11:20:22 +0200	[thread overview]
Message-ID: <200907241120.22483.arnd@arndb.de> (raw)
In-Reply-To: <4A69651E.7040305@monstr.eu>

On Friday 24 July 2009, Michal Simek wrote:
> I have just look at asm-generic uaccess.h and there is one thing which
> seems to me wrong.
> 
> For put_user macro - you use __copy_to_user but you have for 64bit case
> ifdef CONFIG_64BIT
> but  look at fs/eventfd: eventfd_read function. At least for this
> function(syscall) is necessary "return" 64bit
> value on 32bit machines too.
> IMHO that ifdef CONFIG_64BIT shouldn't be there.
> 
> What do you think?
> If you agree with me, I'll generate proper patch with description.

The code was intentional, because 32 bit architectures normally
don't acces u64 values efficiently. I would expect the memcpy
to produce better object code in that case.
Did you see an actual bug in my version or are you only
guessing that the assignment should work better than the
memcpy?

What object code do you get with

int test(unsigned long long __user *out, unsigned long long in)
{
	return put_user(in, ptr);
}

in both cases?

	Arnd <><

  reply	other threads:[~2009-07-24  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24  7:39 generic uaccess.h Michal Simek
2009-07-24  9:20 ` Arnd Bergmann [this message]
2009-07-24  9:44   ` Michal Simek
2009-07-27  9:43   ` Michal Simek
2009-07-27 18:18     ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200907241120.22483.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=john.williams@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox