From: Dan Rosenberg <drosenberg@vsecurity.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: perex@perex.cz, alsa-devel@alsa-project.org, security@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sound/oss: remove offset from load_patch callbacks
Date: Wed, 23 Mar 2011 10:06:22 -0400 [thread overview]
Message-ID: <1300889182.1968.13.camel@dan> (raw)
In-Reply-To: <s5hhbauc4zs.wl%tiwai@suse.de>
On Wed, 2011-03-23 at 14:59 +0100, Takashi Iwai wrote:
> At Wed, 23 Mar 2011 09:47:22 -0400,
> Dan Rosenberg wrote:
> > --- a/sound/oss/midi_synth.c
> > +++ b/sound/oss/midi_synth.c
> > @@ -508,16 +506,15 @@ midi_synth_load_patch(int dev, int format, const char __user *addr,
> > * been transferred already.
> > */
> >
> > - if(copy_from_user(&((char *) &sysex)[offs], &(addr)[offs], hdr_size - offs))
> > + if (copy_from_user(&sysex, addr, hdr_size))
>
> Please correct the comment in the above as well.
> With this change, the transfer is no longer partial.
Will do.
>
> > --- a/sound/oss/opl3.c
> > +++ b/sound/oss/opl3.c
> ...
> > @@ -834,7 +834,7 @@ static int opl3_load_patch(int dev, int format, const char __user *addr,
> > * What the fuck is going on here? We leave junk in the beginning
> > * of ins and then check the field pretty close to that beginning?
> > */
> > - if(copy_from_user(&((char *) &ins)[offs], addr + offs, sizeof(ins) - offs))
> > + if (copy_from_user(&ins, addr, sizeof(ins)))
>
> Ditto.
Likewise.
>
> > return -EFAULT;
> >
> > if (ins.channel < 0 || ins.channel >= SBFM_MAXINSTR)
> > diff --git a/sound/oss/sequencer.c b/sound/oss/sequencer.c
> > index 5ea1098..2e842cb 100644
> > --- a/sound/oss/sequencer.c
> > +++ b/sound/oss/sequencer.c
> > @@ -241,7 +241,7 @@ int sequencer_write(int dev, struct file *file, const char __user *buf, int coun
> > return -ENXIO;
> >
> > fmt = (*(short *) &event_rec[0]) & 0xffff;
> > - err = synth_devs[dev]->load_patch(dev, fmt, buf, p + 4, c, 0);
> > + err = synth_devs[dev]->load_patch(dev, fmt, buf, c, 0);
>
> The address must be "buf + p + 4" instead of "buf", when you omit the
> offset argument.
>
Are you sure? Previously, the copy of the header was from (buf + p + 4)
to (dst + p + 4) with length (hdr_size - (p + 4)), and now the copy is
from buf to dst with length hdr_size. If I do as you suggest, then the
copy will be from (buf + p + 4) to dst for the header.
-Dan
>
> thanks,
>
> Takashi
next prev parent reply other threads:[~2011-03-23 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 13:47 [PATCH v2] sound/oss: remove offset from load_patch callbacks Dan Rosenberg
2011-03-23 13:59 ` Takashi Iwai
2011-03-23 14:06 ` Dan Rosenberg [this message]
2011-03-23 14:46 ` Takashi Iwai
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=1300889182.1968.13.camel@dan \
--to=drosenberg@vsecurity.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=security@kernel.org \
--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