public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergej Pupykin <pupykin.s@gmail.com>
To: Dan Carpenter <error27@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-media@vger.kernel.org
Subject: Re: [patch v2] [media] bttv: take correct lock in bttv_open()
Date: Mon, 13 Dec 2010 01:42:49 +0300	[thread overview]
Message-ID: <4D054FE9.80000@gmail.com> (raw)
In-Reply-To: <20101212165812.GG10623@bicker>

On 12.12.2010 19:58, Dan Carpenter wrote:
> We're trying to make sure that no one is writing to the btv->init struct
> while we copy it over to the newly allocated "fh" struct.  The original
> code doesn't make sense because "fh->cap.vb_lock" hasn't been
> initialized and no one else can be writing to it anyway.
>
This patch also crashes the system. Unfortunately machine hangs, so I 
can not copy-paste trace. It was something about nosemaphore called from 
bttv_open. (something like previous reports)

I replace lock with btv->lock:

mutex_lock(&btv->lock);
*fh = btv->init;
mutex_unlock(&btv->lock);

Probably it is overkill and may be incorrect, but it starts working.

Also I found another issue: tvtime hangs on exit in D-state, so it looks 
like there is a problem near bttv_release function or something like this.

  reply	other threads:[~2010-12-12 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101210033304.GX10623@bicker>
     [not found] ` <4D01D4BE.1080000@gmail.com>
2010-12-12 16:58   ` [patch v2] [media] bttv: take correct lock in bttv_open() Dan Carpenter
2010-12-12 22:42     ` Sergej Pupykin [this message]
2010-12-14 10:36       ` Dan Carpenter
2010-12-14 12:33         ` Mauro Carvalho Chehab

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=4D054FE9.80000@gmail.com \
    --to=pupykin.s@gmail.com \
    --cc=error27@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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