From: Shuah Khan <shuah.kh@samsung.com>
To: m.chehab@samsung.com, dheitmueller@kernellabs.com, olebowle@gmx.com
Cc: Shuah Khan <shuah.kh@samsung.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] media: prevent driver device access in disconnect path
Date: Sat, 12 Jul 2014 10:44:11 -0600 [thread overview]
Message-ID: <cover.1405179280.git.shuah.kh@samsung.com> (raw)
Some fe drivers attempt to access the device for power control from
their release routines. When release routines are called after device
is disconnected, the attempts fail. fe drivers should avoid accessing
the device, from their release interfaces when called from disconnect
path. The problem is noticed in drx39xyj driver.
This patch series does the following to fix the problem:
- exports dvb-frontend exit flag by moving it from fepriv to fe.
- changes em28xx-dvb to update the fe exit path in its usb
disconnect path
- changes drx39xyj driver to check and avoid accessing the device in
its release interface.
Shuah Khan (3):
media: dvb-core move fe exit flag from fepriv to fe for driver access
media: em28xx-dvb update fe exit flag to indicate device disconnect
media: drx39xyj driver change to check fe exit flag from release
drivers/media/dvb-core/dvb_frontend.c | 26 +++++++++++---------------
drivers/media/dvb-core/dvb_frontend.h | 5 +++++
drivers/media/dvb-frontends/drx39xyj/drxj.c | 4 +++-
drivers/media/usb/em28xx/em28x-dvb.c | 8 ++++++--
4 files changed, 25 insertions(+), 18 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-07-12 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 16:44 Shuah Khan [this message]
2014-07-12 16:44 ` [PATCH 1/3] media: dvb-core move fe exit flag from fepriv to fe for driver access Shuah Khan
2014-07-12 16:44 ` [PATCH 2/3] media: em28xx-dvb update fe exit flag to indicate device disconnect Shuah Khan
2014-07-12 16:44 ` [PATCH 3/3] media: drx39xyj driver change to check fe exit flag from release Shuah Khan
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=cover.1405179280.git.shuah.kh@samsung.com \
--to=shuah.kh@samsung.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=olebowle@gmx.com \
/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
Powered by JetHome