From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Cohen
Subject: [PATCH 0/4] iommu: Prevent oops in iommu_get() and while arch_iommu is in use
Date: Fri, 25 Mar 2011 17:13:10 +0200 [thread overview]
Message-ID: <4D8CB106.7030608@maxwell.research.nokia.com> (raw)
Hi,
This patchset is aimed to fix a problem in arch_iommu implementation
references. When an actual arch_iommu implementation is not loaded while
iommu_get() is being called results to a kernel oops, as well as
removing an arch_iommu implementation which is in use.
This patchset fixes both issues.
The patchset assumes the arch_iommu is uninstalled at module unload
time. Is this an acceptable requirement?
Serialisation of the access to arch_iommu is done using mutex called
arch_iommu_mutex.
module_put() doesn't need to have the arch_iommu_mutex since when this
gets called there won't be any users on the arch_iommu anyway.
Comments are welcome. :-)
Cheers,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
next reply other threads:[~2011-03-25 15:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 15:13 Sakari Ailus [this message]
2011-03-25 15:13 ` [PATCH 1/4] omap iommu: Check existence of arch_iommu Sakari Ailus
2011-03-25 15:19 ` Sakari Ailus
2011-03-25 19:07 ` Hiremath, Vaibhav
2011-03-27 17:04 ` Sakari Ailus
2011-03-25 15:13 ` [PATCH 2/4] omap iommu: Add module information to struct iommu_functions Sakari Ailus
2011-03-25 15:13 ` [PATCH 3/4] omap2 iommu: Set module information in omap2_iommu_ops Sakari Ailus
2011-03-25 15:13 ` [PATCH 4/4] omap iommu: Prevent iommu implementations from being unloaded while in use Sakari Ailus
2011-03-25 19:37 ` [PATCH 0/4] iommu: Prevent oops in iommu_get() and while arch_iommu is " Ramirez Luna, Omar
2011-03-27 17:27 ` Sakari Ailus
2011-03-28 1:42 ` Ramirez Luna, Omar
2011-03-28 9:20 ` David Cohen
2011-03-29 15:44 ` Laurent Pinchart
2011-03-28 9:02 ` David Cohen
2011-03-29 15:32 ` Laurent Pinchart
2011-03-30 8:16 ` Sakari Ailus
2011-03-30 9:37 ` Laurent Pinchart
2011-03-30 13:50 ` Sakari Ailus
2011-03-30 13:56 ` Laurent Pinchart
2011-03-30 15:50 ` David Cohen
2011-04-04 14:05 ` Laurent Pinchart
2011-04-05 9:03 ` Sakari Ailus
2011-04-05 11:23 ` Laurent Pinchart
2011-04-05 11:54 ` David Cohen
2011-04-06 8:55 ` Laurent Pinchart
2011-04-05 15:20 ` Sakari Ailus
2011-09-24 13:44 ` Steve Sakoman
2011-09-26 16:19 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2011-03-25 15:17 Sakari Ailus
2011-03-25 15:44 ` David Cohen
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=4D8CB106.7030608@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=hiroshi.doyu@nokia.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.