On Mon, Feb 22, 2016 at 03:20:17PM -0700, Jason Gunthorpe wrote: > On Mon, Feb 22, 2016 at 11:08:59PM +0200, Jarkko Sakkinen wrote: > > On Fri, Feb 19, 2016 at 07:42:01AM -0500, Stefan Berger wrote: > > > From: Jason Gunthorpe <[email protected]> > > > > > > Add a read/write semaphore around the ops function pointers so > > > ops can be set to null when the driver un-registers. > > > > > > Previously the tpm core expected module locking to be enough to > > > ensure that tpm_unregister could not be called during certain times, > > > however that hasn't been sufficient for a long time. > > > > Could you be more concrete with the scenario? You could describe > > a sequence of events where this could happen. > > echo 1 > /sys/.../remove > > Is basically the same as a module unload without requiring module > unload. module locking cannot be relied upon for correctness like this > ever since hot remove was added to the kernel.
The 'remove' file applies only to PCI devices AFAIK. /Jarkko ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ tpmdd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
