From: walter harms <wharms@bfs.de>
To: Dan Carpenter <error27@gmail.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
kernel-janitors@vger.kernel.org,
Clemens Ladisch <clemens@ladisch.de>,
Kyle McMartin <kyle@mcmartin.ca>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: [patch v3] ALSA: rawmidi: fix the get next midi device ioctl
Date: Thu, 09 Sep 2010 07:23:04 +0000 [thread overview]
Message-ID: <4C888B58.9060702@bfs.de> (raw)
In-Reply-To: <20100908221141.GD3463@bicker>
Dan Carpenter schrieb:
> If we pass in a device which is higher than SNDRV_RAWMIDI_DEVICES then
> the "next device" should be -1. This function just returns device + 1.
>
> But the main thing is that "device + 1" can lead to a (harmless) integer
> overflow and that annoys static analysis tools.
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
> ---
> V2: In the first version I made negative values return -EINVAL
> V3: We shouldn't return -EINVAL for numbers which are too large but
> just set the next device to -1.
>
> diff --git a/sound/core/rawmidi.c b/sound/core/rawmidi.c
> index eb68326..df67605 100644
> --- a/sound/core/rawmidi.c
> +++ b/sound/core/rawmidi.c
> @@ -829,6 +829,8 @@ static int snd_rawmidi_control_ioctl(struct snd_card *card,
>
> if (get_user(device, (int __user *)argp))
> return -EFAULT;
> + if (device > SNDRV_RAWMIDI_DEVICES) /* next device is -1 */
> + device = SNDRV_RAWMIDI_DEVICES;
> mutex_lock(®ister_mutex);
> device = device < 0 ? 0 : device + 1;
> while (device < SNDRV_RAWMIDI_DEVICES) {
i am not the expert here but i sound a good idea to put all device changes into one place. like:
if (device > SNDRV_RAWMIDI_DEVICES )
device = SNDRV_RAWMIDI_DEVICES;
else if (device < 0 )
device = 0;
else
device++;
just my 2 cents,
re,
wh
next prev parent reply other threads:[~2010-09-09 7:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 8:53 [patch] ALSA: rawmidi: cleanup the get next midi device ioctl Dan Carpenter
2010-09-08 9:40 ` Clemens Ladisch
2010-09-08 19:36 ` [patch v2] ALSA: rawmidi: fix " Dan Carpenter
2010-09-08 19:56 ` Takashi Iwai
2010-09-08 21:29 ` Jaroslav Kysela
2010-09-08 22:11 ` [patch v3] " Dan Carpenter
2010-09-09 7:07 ` Takashi Iwai
2010-09-09 8:36 ` Jaroslav Kysela
2010-09-09 7:23 ` walter harms [this message]
2010-09-09 6:57 ` [patch v2] " Takashi Iwai
2010-09-09 7:44 ` Clemens Ladisch
2010-09-09 8:46 ` Dan Carpenter
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=4C888B58.9060702@bfs.de \
--to=wharms@bfs.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=drepper@redhat.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kyle@mcmartin.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox