public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, Roland Dreier <rolandd@cisco.com>,
	akpm@linux-foundation.org
Subject: Re: mmotm 2009-08-04-14-22 uploaded (ummunotify)
Date: Tue, 04 Aug 2009 17:38:29 -0700	[thread overview]
Message-ID: <adafxc7ksca.fsf@cisco.com> (raw)
In-Reply-To: <20090804155014.35d4597c.randy.dunlap@oracle.com> (Randy Dunlap's message of "Tue, 4 Aug 2009 15:50:14 -0700")


 > ummunotify.c:(.text+0x8f217): undefined reference to `__get_user_X'
 > 
 > when building for i386.
 > 
 > The get_user() and put_user() in ummunotify_exchange_features()
 > are correctly converted to __get_user_4() and __put_user_4(),
 > but the get_user() in ummunotify_unregister_region() becomes
 > __get_user_X()  [as seen in objdump output].

Is 64-bit get_user() supposed to work portably?  Because it seems that
arch/x86/include/asm/uaccess.h intentionally makes get_user((__u64))
expand to __get_user_X() and then never defines __get_user_X().  And
arm, say, expands it to __get_user_bad().  But on the other hand,
powerpc and sparc seem to go to the trouble of defining a 64-bit
get_user() for 32-bit builds...

My fault for insufficient 32-bit compile testing.  Andrew, I'll send a
patch to change to copy_from_user() instead.

 - R.

  parent reply	other threads:[~2009-08-05  0:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 21:25 mmotm 2009-08-04-14-22 uploaded akpm
2009-08-04 22:50 ` mmotm 2009-08-04-14-22 uploaded (ummunotify) Randy Dunlap
2009-08-04 23:16   ` Andrew Morton
2009-08-05  0:38   ` Roland Dreier [this message]
2009-08-05  4:47   ` Roland Dreier
2009-08-05 15:19     ` Randy Dunlap
2009-08-05  1:48 ` [PATCH -mmotm] staging/udlfb: fix printk format warning Randy Dunlap
2009-08-05  1:54 ` [PATCH -mmotm] xfrm4: fix build when SYSCTLs are disabled Randy Dunlap
2009-08-05  3:20   ` David Miller
2009-08-05  6:39 ` mmotm 2009-08-04-14-22 uploaded Dave Young
2009-08-05  7:06   ` Andrew Morton
2009-08-05  7:14   ` Eric Dumazet

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=adafxc7ksca.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rolandd@cisco.com \
    /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