From: Antti Palosaari <crope@iki.fi>
To: Nils Kassube <kassube@gmx.net>
Cc: linux-media@vger.kernel.org
Subject: Re: Fix for crash in dvb-usb-af9015
Date: Tue, 07 Jul 2009 14:00:26 +0300 [thread overview]
Message-ID: <4A532ACA.1070607@iki.fi> (raw)
In-Reply-To: <200907071232.00459.kassube@gmx.net>
Moi Nils,
Nils Kassube wrote:
> I found out that the crash happens when the device should boot after
> downloading the firmware because there seems to be no sufficiently big
> buffer for the boot message (or whatever it is) returned from the
> device. As this message is ignored by the calling function anyway, this
> patch fixes the problem:
>
> --- orig/linux-2.6.31/drivers/media/dvb/dvb-usb/af9015.c 2009-06-30
> 11:34:45.000000000 +0200
> +++ linux-2.6.31/drivers/media/dvb/dvb-usb/af9015.c 2009-07-06
> 21:42:50.000000000 +0200
> @@ -158,7 +158,7 @@
> }
>
> /* read request, copy returned data to return buf */
> - if (!write)
> + if (!write && req->cmd != BOOT)
> memcpy(req->data, &buf[2], req->data_len);
>
> error_unlock:
>
> However, it would certainly be better to provide an appropriate buffer
> when calling this function from af9015_download_firmware because I think
> it is called very often here and the extra check for the BOOT command is
> needed only once (after firmware download). As I'm not familiar with the
> hardware, I can't say what buffer size would be appropriate but I can
> say that for my device the parameter "req->data_len" was 32 in the
> memcpy command above when I tried to find the fix.
I see the problem but your fix is not ideally correct for my eyes. I
don't have currently access to sniffs to ensure that but I think BOOT
should be write command. Now it is defined as read. I think moving BOOT
from read to write fixes problem.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2009-07-07 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 10:32 Fix for crash in dvb-usb-af9015 Nils Kassube
2009-07-07 11:00 ` Antti Palosaari [this message]
2009-07-07 14:33 ` Nils Kassube
2009-07-10 23:49 ` Antti Palosaari
2009-07-11 6:02 ` Nils Kassube
2009-07-13 20:50 ` Antti Palosaari
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=4A532ACA.1070607@iki.fi \
--to=crope@iki.fi \
--cc=kassube@gmx.net \
--cc=linux-media@vger.kernel.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.