Re: [PATCH] [media] dvb-frontends/stv0910: prevent consecutive mutex_unlock()'s

2017-11-07 Thread Mauro Carvalho Chehab
Em Sat, 21 Oct 2017 11:57:57 +0200 Daniel Scheller escreveu: > Am Sat, 21 Oct 2017 11:28:10 +0200 > schrieb Ralph Metzler : > > > Daniel Scheller writes: > > > From: Daniel Scheller > > > > > > When calling gate_ctrl() with enable=0 if previously the mutex > > > wasn't locked (ie. on ena

Re: [PATCH] [media] dvb-frontends/stv0910: prevent consecutive mutex_unlock()'s

2017-10-21 Thread Daniel Scheller
Am Sat, 21 Oct 2017 11:28:10 +0200 schrieb Ralph Metzler : > Daniel Scheller writes: > > From: Daniel Scheller > > > > When calling gate_ctrl() with enable=0 if previously the mutex > > wasn't locked (ie. on enable=1 failure and subdrivers not handling > > this properly, or by otherwise bad

[PATCH] [media] dvb-frontends/stv0910: prevent consecutive mutex_unlock()'s

2017-10-21 Thread Ralph Metzler
Daniel Scheller writes: > From: Daniel Scheller > > When calling gate_ctrl() with enable=0 if previously the mutex wasn't > locked (ie. on enable=1 failure and subdrivers not handling this properly, > or by otherwise badly behaving drivers), the i2c_lock could be unlocked I think drivers an

[PATCH] [media] dvb-frontends/stv0910: prevent consecutive mutex_unlock()'s

2017-10-21 Thread Daniel Scheller
From: Daniel Scheller When calling gate_ctrl() with enable=0 if previously the mutex wasn't locked (ie. on enable=1 failure and subdrivers not handling this properly, or by otherwise badly behaving drivers), the i2c_lock could be unlocked consecutively which isn't allowed. Prevent this by keeping