public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Russell <brian.russell@brocade.com>
To: "Hans J. Koch" <hjk@hansjkoch.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH v8 0/2] uio: Fix uio hotplug issues
Date: Thu, 19 Mar 2015 17:55:21 +0000	[thread overview]
Message-ID: <550B0D89.2090501@brocade.com> (raw)

Protect uio driver from crashing when its owner is unplugged while there
are open fds.

Brian Russell (2):
	uio: Request/free irq separate from dev lifecycle
	uio: Fix uio driver to refcount device

v8: break out irq change into separate patch

v7: use dev_set_name and fix error path in uio_register_device

v6: ... and put them in the right place

v5: add patch version changes

v4: info struct passed in uio_register_device can be freed
    on unregister, so null out the field in uio_unregister_device and
    check accesses.

v3: Embed struct device in struct uio_device, use refcounting on
    device, free uio_device on release.

v2: Add blank line to header

                 reply	other threads:[~2015-03-19 17:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=550B0D89.2090501@brocade.com \
    --to=brian.russell@brocade.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hjk@hansjkoch.de \
    --cc=linux-kernel@vger.kernel.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