From: mka@chromium.org (Matthias Kaehlcke)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Fix multiple 'asm-operand-widths' warnings
Date: Tue, 2 May 2017 11:52:12 -0700 [thread overview]
Message-ID: <20170502185212.GY128305@google.com> (raw)
In-Reply-To: <20170502172948.GE28132@leverpostej>
Hi,
El Tue, May 02, 2017 at 06:29:48PM +0100 Mark Rutland ha dit:
> On Mon, May 01, 2017 at 02:26:22PM -0700, Matthias Kaehlcke wrote:
> > diff --git a/arch/arm64/include/asm/uaccess.h b/arch/arm64/include/asm/uaccess.h
> > index 5308d696311b..7db143689694 100644
> > --- a/arch/arm64/include/asm/uaccess.h
> > +++ b/arch/arm64/include/asm/uaccess.h
> > @@ -302,7 +302,7 @@ do { \
> > " .previous\n" \
> > _ASM_EXTABLE(1b, 3b) \
> > : "+r" (err) \
> > - : "r" (x), "r" (addr), "i" (-EFAULT))
> > + : "r" ((__u64)x), "r" (addr), "i" (-EFAULT))
> >
>
> For reference, do you have the warning for this case to hand?
>
> In __put_user_err() we make __pu_val the same type as *ptr, then we
> switch on sizeof(*ptr), and pass __pu_val to __put_user_asm(), as x.
> For cases 1, 2, and 4, we use "%w" as the register template.
>
> So I can't see why we'd need this cast in __put_user_err().
>
> I must be missing something.
This is one of many instances:
./include/linux/pagemap.h:554:10: warning: value size does not match register size specified by the constraint and modifier [-Wasm-operand-widths]
return __put_user(0, end);
^
./arch/arm64/include/asm/uaccess.h:338:2: note: expanded from macro '__put_user'
__put_user_err((x), (ptr), __pu_err); \
^
./arch/arm64/include/asm/uaccess.h:326:38: note: expanded from macro '__put_user_err'
__put_user_asm("str", "sttr", "%", __pu_val, (ptr), \
^
./include/linux/pagemap.h:554:10: note: use constraint modifier "w"
./arch/arm64/include/asm/uaccess.h:338:2: note: expanded from macro '__put_user'
__put_user_err((x), (ptr), __pu_err); \
^
./arch/arm64/include/asm/uaccess.h:326:34: note: expanded from macro '__put_user_err'
__put_user_asm("str", "sttr", "%", __pu_val, (ptr), \
^
'end' is a char pointer, it is not clear to me why we would end up in
the width == 8 branch.
Matthias
next prev parent reply other threads:[~2017-05-02 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 21:26 [PATCH] arm64: Fix multiple 'asm-operand-widths' warnings Matthias Kaehlcke
2017-05-02 8:25 ` Marc Zyngier
2017-05-02 10:27 ` Mark Rutland
2017-05-02 17:26 ` Matthias Kaehlcke
2017-05-02 17:29 ` Mark Rutland
2017-05-02 18:52 ` Matthias Kaehlcke [this message]
2017-05-03 10:51 ` Mark Rutland
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=20170502185212.GY128305@google.com \
--to=mka@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).