linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: LMML <linux-media@vger.kernel.org>, Guy Martin <gmsoft@tuxicoman.be>
Subject: Re: Status of the patches under review (85 patches) and some misc notes about the devel procedures
Date: Fri, 07 May 2010 22:26:13 -0300	[thread overview]
Message-ID: <4BE4BDB5.60509@redhat.com> (raw)
In-Reply-To: <x2w1a297b361005070610lda8d8d2ve90011bbfff320ee@mail.gmail.com>

Manu Abraham wrote:
> On Fri, May 7, 2010 at 4:39 PM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> Hi,
>>
> 
>> This is the summary of the patches that are currently under review.
>> Each patch is represented by its submission date, the subject (up to 70
>> chars) and the patchwork link (if submitted via email).
>>
>> P.S.: This email is c/c to the developers that some review action is expected.
>>
>> May, 7 2010: [v2] stv6110x Fix kernel null pointer deref when plugging two TT s2-16 http://patchwork.kernel.org/patch/97612
> 
> 
> How is this patch going to fix a NULL ptr dereference when more than 1
> card is plugged in ? The patch doesn't seem to do what the patch title
> implies. At least the patch title seems to be wrong. Maybe the patch
> is supposed to check for a possible NULL ptr dereference when put to
> sleep ?

(c/c patch author, to be sure that he'll see your explanation request)

His original patch is at:
	https://patchwork.kernel.org/patch/91929/

The original description with the bug were much better than version 2.

>From his OOPS log and description, I suspect that he's facing some
sort of race condition with the two cards. 

This fix seems still valid (with an updated comment), as his dump
proofed that there are some cases where fe->tuner_priv can be null, 
generating an OOPS, but it seems that his patch is combating
the effect, and not the cause.

So, I am for adding his patch for now, and then work on a more complete
approach for the two cards environment.

-- 

Cheers,
Mauro

  reply	other threads:[~2010-05-08  1:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 12:39 Status of the patches under review (85 patches) and some misc notes about the devel procedures Mauro Carvalho Chehab
2010-05-07 12:58 ` Guennadi Liakhovetski
2010-05-08  1:13   ` Mauro Carvalho Chehab
2010-05-07 13:03 ` Manu Abraham
2010-05-08  1:27   ` Mauro Carvalho Chehab
2010-05-07 13:10 ` Manu Abraham
2010-05-08  1:26   ` Mauro Carvalho Chehab [this message]
2010-05-27 14:05     ` Guy Martin
2010-05-27 21:42       ` Mauro Carvalho Chehab
2010-05-07 13:15 ` Manu Abraham
2010-05-08  1:28   ` Mauro Carvalho Chehab
2010-05-07 13:16 ` Manu Abraham
2010-05-08  1:30   ` Mauro Carvalho Chehab
2010-05-08  5:34 ` Herton Ronaldo Krzesinski
2010-05-08 22:41   ` Mauro Carvalho Chehab
2010-05-10 18:46     ` Herton Ronaldo Krzesinski
2010-05-10 19:54       ` Mauro Carvalho Chehab
2010-05-08  6:31 ` Jean-Francois Moine
2010-05-08 22:45   ` Mauro Carvalho Chehab
2010-05-10 13:45     ` Sarah Sharp
2010-05-10 16:25       ` Mauro Carvalho Chehab
2010-05-10 17:39         ` Jean-Francois Moine
2010-05-11  1:20           ` Sarah Sharp
2010-05-10  6:57 ` Pawel Osciak
2010-05-10 12:58 ` Pawel Osciak
2010-07-01 11:46 ` Bjørn Mork
2010-07-06 13:46   ` Mauro Carvalho Chehab
2010-07-07 12:52     ` Bjørn Mork

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=4BE4BDB5.60509@redhat.com \
    --to=mchehab@redhat.com \
    --cc=abraham.manu@gmail.com \
    --cc=gmsoft@tuxicoman.be \
    --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;
as well as URLs for NNTP newsgroup(s).