public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Udo van den Heuvel <udovdh@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: pwc driver bugs
Date: Thu, 24 May 2012 21:10:08 +0200	[thread overview]
Message-ID: <4FBE8790.6000000@redhat.com> (raw)
In-Reply-To: <20120524165638.0ade5a6f@pyramind.ukuu.org.uk>

Alan,

Thanks for adding me to the CC on this. Udo, I've
responded to your bugs in bugzilla.

Regards,

Hans


On 05/24/2012 05:56 PM, Alan Cox wrote:
> On Thu, 24 May 2012 17:03:49 +0200
> Udo van den Heuvel<udovdh@xs4all.nl>  wrote:
>
>> Hello,
>>
>> I discovered some issues in the pwc driver for certain USB webcams.
>> I opened some bugs[1].
>> I do think both issues might be related and the crash issue is quite
>> serious.
>>
>> Please have a look, I can assist by testing any patches with fixes. (for
>> ~3.3.7)
>
> commit ceede9fa8939e40ad0ddb4ad1355f45c6f1d3478
>
> looks rather relevant here.
>
> commit ceede9fa8939e40ad0ddb4ad1355f45c6f1d3478
> Author: Hans de Goede<hdegoede@redhat.com>
> Date:   Wed May 9 04:43:12 2012 -0300
>
>      [media] pwc: Fix locking
>
>      My last locking rework for pwc mistakenly assumed that videbuf2 does
>      its own locking, but it does not! This patch fixes the missing
>      locking by moving over the the video_device lock, and introducing a
>      separate lock for the videobuf2_queue.
>
>      Signed-off-by: Hans de Goede<hdegoede@redhat.com>
>      Signed-off-by: Mauro Carvalho Chehab<mchehab@redhat.com>

      parent reply	other threads:[~2012-05-24 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 15:03 pwc driver bugs Udo van den Heuvel
2012-05-24 15:56 ` Alan Cox
2012-05-24 16:37   ` Udo van den Heuvel
2012-05-24 19:10   ` Hans de Goede [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=4FBE8790.6000000@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=udovdh@xs4all.nl \
    /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