All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Olof Johansson <olof@lixom.net>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: control: remove compilation warning on 32-bit
Date: Sat, 05 Nov 2011 23:00:09 +0100	[thread overview]
Message-ID: <4EB5B1E9.9080401@ladisch.de> (raw)
In-Reply-To: <1320460125-20881-1-git-send-email-olof@lixom.net>

Olof Johansson wrote:
> This was introduced by 'ALSA: control: add support for ENUMERATED user
> space controls' which adds a u64 variable that gets cast to a pointer:
>
> sound/core/control.c: In function 'snd_ctl_elem_init_enum_names':
> sound/core/control.c:1089: warning: cast to pointer from integer of different size
>
> Since we don't support 64-bit userspace on 32-bit kernel, it's safe to
> cast to long before casting to pointer to avoid the warning.
>
> Signed-off-by: Olof Johansson <olof@lixom.net>
> ---
>  sound/core/control.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)

Applied (with uintptr_t instead of long); thanks!


Clemens


> diff --git a/sound/core/control.c b/sound/core/control.c
> index 978fe1a..d09c335 100644
> --- a/sound/core/control.c
> +++ b/sound/core/control.c
> @@ -1081,12 +1081,12 @@ static int snd_ctl_elem_init_enum_names(struct user_element *ue)
>  	char *names, *p;
>  	size_t buf_len, name_len;
>  	unsigned int i;
> +	const long user_ptrval = ue->info.value.enumerated.names_ptr;
>
>  	if (ue->info.value.enumerated.names_length > 64 * 1024)
>  		return -EINVAL;
>
> -	names = memdup_user(
> -		(const void __user *)ue->info.value.enumerated.names_ptr,
> +	names = memdup_user((const void __user *)user_ptrval,
>  		ue->info.value.enumerated.names_length);
>  	if (IS_ERR(names))
>  		return PTR_ERR(names);

      reply	other threads:[~2011-11-05 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-05  2:28 [PATCH] ALSA: control: remove compilation warning on 32-bit Olof Johansson
2011-11-05 22:00 ` Clemens Ladisch [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=4EB5B1E9.9080401@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=olof@lixom.net \
    --cc=tiwai@suse.de \
    /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.