linux-kernel - Re: [PATCH 1/1] DVB-USB: dib0700, fix oops with non-dib7000pc devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D6661E4.6040505@infradead.org>
Date:	Thu, 24 Feb 2011 10:49:24 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Jiri Slaby <jslaby@...e.cz>
CC:	Jiri Slaby <jirislaby@...il.com>, linux-media@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Patrick Boettcher <pboettcher@...nellabs.com>
Subject: Re: [PATCH 1/1] DVB-USB: dib0700, fix oops with non-dib7000pc devices

Em 24-02-2011 10:41, Jiri Slaby escreveu:
> On 02/24/2011 01:53 PM, Mauro Carvalho Chehab wrote:
>> Em 24-02-2011 09:24, Jiri Slaby escreveu:
>>> Hmm, could anybody pick it up?
>>>
>>> On 02/05/2011 07:20 PM, Jiri Slaby wrote:
>>>> These devices use different internal structures (dib7000m) and
>>>> dib7000p pid ctrl accesses invalid members causing kernel to die.
>>>>
>>>> Introduce pid control functions for dib7000m which operate on the
>>>> correct structure.
>>
>> Patrick (DibCom drivers maintainer) has proposed an alternate patch for it [1]
>> that properly address the issues:
>>
>> http://git.linuxtv.org/pb/media_tree.git?a=commitdiff;h=80a5f1fdc6beb496347cbb297f9c1458c8cb9f50
>>
>> [1] http://www.spinics.net/lists/linux-media/msg27890.html
>>
>> Could you please test it?
> 
> Yes, I will later.
> 
> Is there any reason why this is not in Linus' and stable trees and
> mainly in linux/next already?

Yes. I'm waiting for confirmation that this patch fixes the reported issue.

Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/