mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Shuah Khan" <shuahkh@osg.samsung.com>
Cc: <geliangtang@163.com>, <ricard.wanderlof@axis.com>,
	<hans.verkuil@cisco.com>, <chehabrafael@gmail.com>,
	<takamichiho@gmail.com>, <dominic.sacre@gmx.de>,
	<laurent.pinchart@ideasonboard.com>, <julian@jusst.de>,
	<clemens@ladisch.de>, <pierre-louis.bossart@linux.intel.com>,
	<johan@oljud.se>, <javier@osg.samsung.com>,
	<mchehab@osg.samsung.com>, <perex@perex.cz>,
	<jh1009.sung@samsung.com>, <alsa-devel@alsa-project.org>,
	<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>
Subject: Re: [RFC PATCH v2 0/5] Media Device Allocator API
Date: Tue, 05 Apr 2016 08:10:11 +0200	[thread overview]
Message-ID: <s5hfuv0ziv0.wl-tiwai@suse.de> (raw)
In-Reply-To: <cover.1459825702.git.shuahkh@osg.samsung.com>

On Tue, 05 Apr 2016 05:35:55 +0200,
Shuah Khan wrote:
> 
> There are known problems with media device life time management. When media
> device is released while an media ioctl is in progress, ioctls fail with
> use-after-free errors and kernel hangs in some cases.
> 
> Media Device can be in any the following states:
> 
> - Allocated
> - Registered (could be tied to more than one driver)
> - Unregistered, not in use (media device file is not open)
> - Unregistered, in use (media device file is not open)
> - Released
> 
> When media device belongs to  more than one driver, registrations should be
> tracked to avoid unregistering when one of the drivers does unregister. A new
> num_drivers field in the struct media_device covers this case. The media device
> should be unregistered only when the last unregister occurs with num_drivers
> count zero.
> 
> When a media device is in use when it is unregistered, it should not be
> released until the application exits when it detects the unregistered
> status. Media device that is in use when it is unregistered is moved to
> to_delete_list. When the last unregister occurs, media device is unregistered
> and becomes an unregistered, still allocated device. Unregister marks the
> device to be deleted.
> 
> When media device belongs to more than one driver, as both drivers could be
> unbound/bound, driver should not end up getting stale media device that is
> on its way out. Moving the unregistered media device to to_delete_list helps
> this case as well.
> 
> I ran bind/unbind loop tests on uvcvideo, au0828, and snd-usb-audio while
> running application that does ioctls. Didn't see any use-after-free errors
> on media device. A couple of known issues seen:
> 
> 1. When application exits, cdev_put() gets called after media device is
>    released. This is a known issue to resolve and Media Device Allocator
>    can't solve this one.
> 2. When au0828 module is removed and then ioctls fail when cdev_get() looks
>    for the owning module as au0828 is very often the module that owns the
>    media devnode. This is a cdev related issue that needs to be resolved and
>    Media Device Allocator can't solve this one.
> 
> Shuah Khan (5):
>   media: Add Media Device Allocator API
>   media: Add driver count to keep track of media device registrations
>   media: uvcvideo change to use Media Device Allocator API
>   media: au0828 change to use Media Device Allocator API
>   sound/usb: Use Media Controller API to share media resources

I don't think we need to include usb-audio patch at this stage yet.
The most important thing for now is to improve / stabilize the API
itself so that other drivers can use it as is.  Once when the API is
really stabilized, we create a solid git branch that may be based for
multiple subsystems, and I'll merge usb-audio stuff through sound git
tree.

Also, the previous usb-audio MC implementation had a few serious bugs,
including quirk NULL dereference.  See the bugzilla below for some fix
patches to 4.6-rc1:
  https://bugzilla.kernel.org/show_bug.cgi?id=115561
Feel free to fold them in, if they are still valid.


thanks,

Takashi

  parent reply	other threads:[~2016-04-05  6:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  3:35 Shuah Khan
2016-04-05  3:35 ` [RFC PATCH v2 1/5] media: Add " Shuah Khan
2016-04-05  3:35 ` [RFC PATCH v2 2/5] media: Add driver count to keep track of media device registrations Shuah Khan
2016-04-05  3:35 ` [RFC PATCH v2 3/5] media: uvcvideo change to use Media Device Allocator API Shuah Khan
2016-04-05  3:35 ` [RFC PATCH v2 4/5] media: au0828 " Shuah Khan
2016-04-05  3:36 ` [RFC PATCH v2 5/5] sound/usb: Use Media Controller API to share media resources Shuah Khan
2016-04-05  6:10 ` Takashi Iwai [this message]
2016-04-05 13:21   ` [RFC PATCH v2 0/5] Media Device Allocator API Shuah Khan
2016-04-05 16:52   ` 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=s5hfuv0ziv0.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=chehabrafael@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=dominic.sacre@gmx.de \
    --cc=geliangtang@163.com \
    --cc=hans.verkuil@cisco.com \
    --cc=javier@osg.samsung.com \
    --cc=jh1009.sung@samsung.com \
    --cc=johan@oljud.se \
    --cc=julian@jusst.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ricard.wanderlof@axis.com \
    --cc=shuahkh@osg.samsung.com \
    --cc=takamichiho@gmail.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

all inboxes | Powered by JetHome®