[PATCH 1/3] dma-buf: don't hold the mutex around map/unmap calls

On Thu, Mar 1, 2012 at 9:35 AM, Daniel Vetter wrote: > The mutex protects the attachment list and hence needs to be held > around the callbakc to the exporters (optional) attach/detach > functions. > > Holding the mutex around the map/unmap calls doesn't protect any > dma_buf state. Exporters need

Re: [PATCH 1/3] dma-buf: don't hold the mutex around map/unmap calls

On Thu, Mar 1, 2012 at 9:35 AM, Daniel Vetter wrote: > The mutex protects the attachment list and hence needs to be held > around the callbakc to the exporters (optional) attach/detach > functions. > > Holding the mutex around the map/unmap calls doesn't protect any > dma_buf state. Exporters need

[PATCH 1/3] dma-buf: don't hold the mutex around map/unmap calls

The mutex protects the attachment list and hence needs to be held around the callbakc to the exporters (optional) attach/detach functions. Holding the mutex around the map/unmap calls doesn't protect any dma_buf state. Exporters need to properly protect any of their own state anyway (to protect ag

[PATCH 1/3] dma-buf: don't hold the mutex around map/unmap calls

The mutex protects the attachment list and hence needs to be held around the callbakc to the exporters (optional) attach/detach functions. Holding the mutex around the map/unmap calls doesn't protect any dma_buf state. Exporters need to properly protect any of their own state anyway (to protect ag