From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: LMML <linux-media@vger.kernel.org>
Subject: Re: [PATCH] V4L/DVB: dib0700: Prevent NULL pointer dereference during probe
Date: Fri, 08 Oct 2010 09:38:28 -0300 [thread overview]
Message-ID: <4CAF10C4.2080701@redhat.com> (raw)
In-Reply-To: <20101008143251.55fed758@endymion.delvare>
Em 08-10-2010 09:32, Jean Delvare escreveu:
> On Sun, 26 Sep 2010 16:25:53 +0200, Jean Delvare wrote:
>> Commit 8dc09004978538d211ccc36b5046919489e30a55 assumes that
>> dev->rc_input_dev is always set. It is, however, NULL if dvb-usb was
>> loaded with option disable_rc_polling=1.
>>
>> Signed-off-by: Jean Delvare <khali@linux-fr.org>
>> Cc: Mauro Carvalho Chehab <mchehab@redhat.com>
>> ---
>> drivers/media/dvb/dvb-usb/dib0700_core.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> --- linux-2.6.36-rc5.orig/drivers/media/dvb/dvb-usb/dib0700_core.c 2010-09-24 17:17:16.000000000 +0200
>> +++ linux-2.6.36-rc5/drivers/media/dvb/dvb-usb/dib0700_core.c 2010-09-26 15:04:59.000000000 +0200
>> @@ -674,7 +674,8 @@ static int dib0700_probe(struct usb_inte
>> dev->props.rc.core.bulk_mode = false;
>>
>> /* Need a higher delay, to avoid wrong repeat */
>> - dev->rc_input_dev->rep[REP_DELAY] = 500;
>> + if (dev->rc_input_dev)
>> + dev->rc_input_dev->rep[REP_DELAY] = 500;
>>
>> dib0700_rc_setup(dev);
>>
>
> The already applied commit 04cab131ce2a267b6777a98d68fbc0cae44d4ba8
> (V4L/DVB: rc-core: increase repeat time) solves the problem in a
> different way, so you can ignore my patch above, it is no longer needed.
>
OK.
Yeah, we needed to move this to IR core, as other drivers were suffering the
same issue, due to RC core timeouts.
Cheers,
Mauro
prev parent reply other threads:[~2010-10-08 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 14:25 [PATCH] V4L/DVB: dib0700: Prevent NULL pointer dereference during probe Jean Delvare
2010-10-08 12:32 ` Jean Delvare
2010-10-08 12:38 ` Mauro Carvalho Chehab [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=4CAF10C4.2080701@redhat.com \
--to=mchehab@redhat.com \
--cc=khali@linux-fr.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox