RE: [PATCH 09/17] mm: export access_remote_vm() symbol

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, Alistair,

> Alistair Popple <apopple@xxxxxxxxxx> writes:
> Lorenzo Stoakes <lstoakes@xxxxxxxxx> writes:
> > My concern is exposing something highly delicate _which accesses
> > remote mas a public API with implicit assumptions whose one and only
> > (core kernel) user treats with enormous caution. Even if this iommu
> > code were to use it correctly, we'd end up with an interface which could be
> subject to real risks which other drivers may misuse.
> 
> Ok, although I think making this an iommu specific wrapper taking a PASID
> rather than mm_struct would make the API more specific and less likely to be
> misused as the mm_count/users lifetime issues could be dealt with inside the
> core IOMMU code.

The iommu specific wrapper still needs to call access_remote_vm() which is
in generic mm. We cannot avoid to export access_remote_vm(), right?
Are you saying the iommu specific wrapper doesn't need to the mm code?
 
Thanks.

-Fenghua





[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux