On 10.01.2013 15:25, Mauro Carvalho Chehab wrote:
Em Thu, 10 Jan 2013 03:06:51 +0100
thomas schorpp escreveu:
On 09.01.2013 22:30, Nikolaus Schulz wrote:
On Tue, Jan 08, 2013 at 12:05:47PM +0530, Soby Mathew wrote:
Hi Everyone,
I have a doubt regarding about the global mutex lock in
dv
Em Thu, 10 Jan 2013 03:06:51 +0100
thomas schorpp escreveu:
> On 09.01.2013 22:30, Nikolaus Schulz wrote:
> > On Tue, Jan 08, 2013 at 12:05:47PM +0530, Soby Mathew wrote:
> >> Hi Everyone,
> >> I have a doubt regarding about the global mutex lock in
> >> dvb_usercopy(drivers/media/dvb-core/d
On 09.01.2013 22:30, Nikolaus Schulz wrote:
On Tue, Jan 08, 2013 at 12:05:47PM +0530, Soby Mathew wrote:
Hi Everyone,
I have a doubt regarding about the global mutex lock in
dvb_usercopy(drivers/media/dvb-core/dvbdev.c, line 382) .
/* call driver */
mutex_lock(&dvbdev_mutex);
if ((err = f
On Tue, Jan 08, 2013 at 12:05:47PM +0530, Soby Mathew wrote:
> Hi Everyone,
> I have a doubt regarding about the global mutex lock in
> dvb_usercopy(drivers/media/dvb-core/dvbdev.c, line 382) .
>
>
> /* call driver */
> mutex_lock(&dvbdev_mutex);
> if ((err = func(file, cmd, parg)) == -ENOIOC
Hi Everyone,
I have a doubt regarding about the global mutex lock in
dvb_usercopy(drivers/media/dvb-core/dvbdev.c, line 382) .
/* call driver */
mutex_lock(&dvbdev_mutex);
if ((err = func(file, cmd, parg)) == -ENOIOCTLCMD)
err = -EINVAL;
mutex_unlock(&dvbdev_mutex);
Why is this mutex needed