On Mon, Jun 30, 2014 at 02:35:57PM -0400, Jerome Glisse wrote:
> We do intend to tear down all secondary mapping inside the relase
> callback but still we can not cleanup all the resources associated
> with it.
>
And why can't you cleanup the other resources in the file close path?
Tearing down the mappings is all you need to do in the release function
anyway.
> As said from the release call back you can not call
> mmu_notifier_unregister and thus you can not fully cleanup things.
You don't need to call mmu_notifier_unregister when the release function
is already running from exit_mmap because this is equivalent to calling
mmu_notifier_unregister.
> Only way to achieve so is to do it ouside mmu_notifier callback.
The resources that can't be handled there can be cleaned up in the
file-close path. No need for a new notifier in mm code.
In the end all you need to do in the release function is to tear down
the secondary mapping and make sure the device can no longer access the
address space when the release function returns. Everything else, like
freeing any resources can be done later when the file descriptors are
teared down.
> If you know any other way to call mmu_notifier_unregister before the
> end of mmput function than i am all ear. I am not adding this call
> back just for the fun of it i spend serious time trying to find a
> way to do thing without it. I might have miss a way so if i did please
> show it to me.
Why do you need to call mmu_notifier_unregister manually when it is done
implicitly in exit_mmap already?
Joerg
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
