All of lore.kernel.org
 help / color / mirror / Atom feed
From: wcohen@redhat.com (William Cohen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Make the 32-bit ARM get_user() and put_user() work for 16-bit quantities
Date: Tue, 29 Oct 2013 14:38:58 -0400	[thread overview]
Message-ID: <527000C2.5000501@redhat.com> (raw)
In-Reply-To: <20131029180414.GS16735@n2100.arm.linux.org.uk>

On 10/29/2013 02:04 PM, Russell King - ARM Linux wrote:
> On Tue, Oct 29, 2013 at 12:52:09PM -0400, William Cohen wrote:
>> The 32-bit ARM does not have instructions to perform 16-bit loads or
>> stores.  The __get_user_asm_half and __put_user_asm_half macros
>> sythesize those operations.  However, in most cases the pointers
>> passed into these macros are pointers to 16-bit types and the pointer
>> arithmetic will end up pointing at the next 16-bit quantity rather
>> than the second half (byte) of the 16-bit quantity.  The macros need
>> to explicitly typecast the pointers as pointers to 8-bit quantities to
>> make the pointer arithmetic work out properly.
> 
> NAK.
> 
> Nothing should be making use of these macros other than the other
> macros in that file; these are implementation specific helper macros.
> There, the address passed as __gu_addr and __pu_addr is an 'unsigned
> long' quantity, so there is no concern about pointer arithmetic; they
> do not take pointers.
> 

You are correct.  systemtap had had macros that were based on the arm uaccess.h macos, but they were missing the typecasts that __get_user_err and __put_user_err.  Thanks for pointing out my error.

-Will

      reply	other threads:[~2013-10-29 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 16:52 [PATCH] Make the 32-bit ARM get_user() and put_user() work for 16-bit quantities William Cohen
2013-10-29 17:49 ` Marc Zyngier
2013-10-29 18:04 ` Russell King - ARM Linux
2013-10-29 18:38   ` William Cohen [this message]

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=527000C2.5000501@redhat.com \
    --to=wcohen@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.