> In drm_prime_handle_to_fd_ioctl(), flags is cleared to only support
> DRM_CLOEXEC but in gem_prime_export() callbacks of each driver, it uses
> 0600 as flags for dma_buf_export() like following.
>
> return dma_buf_export(obj, &i915_dmabuf_ops, obj->base.size, 0600);
Oops, nice catch, radeon and
> In drm_prime_handle_to_fd_ioctl(), flags is cleared to only support
> DRM_CLOEXEC but in gem_prime_export() callbacks of each driver, it uses
> 0600 as flags for dma_buf_export() like following.
>
> return dma_buf_export(obj, &i915_dmabuf_ops, obj->base.size, 0600);
Oops, nice catch, radeon and
On Thu, Sep 27, 2012 at 4:30 PM, Seung-Woo Kim
wrote:
> Increasing ref counts of both dma-buf and gem for imported dma-buf come from
> gem
> makes memory leak. release function of dma-buf cannot be called because
> f_count
> of dma-buf increased by importing gem and gem ref count cannot be decr
Hi Dave,
On 2012? 12? 18? 15:30, Dave Airlie wrote:
> On Thu, Sep 27, 2012 at 4:30 PM, Seung-Woo Kim
> wrote:
>> Increasing ref counts of both dma-buf and gem for imported dma-buf come from
>> gem
>> makes memory leak. release function of dma-buf cannot be called because
>> f_count
>> of dma-b
Hi Dave,
On 2012년 12월 18일 15:30, Dave Airlie wrote:
> On Thu, Sep 27, 2012 at 4:30 PM, Seung-Woo Kim wrote:
>> Increasing ref counts of both dma-buf and gem for imported dma-buf come from
>> gem
>> makes memory leak. release function of dma-buf cannot be called because
>> f_count
>> of dma-buf
On Thu, Sep 27, 2012 at 4:30 PM, Seung-Woo Kim wrote:
> Increasing ref counts of both dma-buf and gem for imported dma-buf come from
> gem
> makes memory leak. release function of dma-buf cannot be called because
> f_count
> of dma-buf increased by importing gem and gem ref count cannot be decre
On 2012? 11? 20? 19:26, Maarten Lankhorst wrote:
> Op 20-11-12 02:03, ??? schreef:
>> Hi Maarten,
>>
>> On 2012? 11? 19? 19:27, Maarten Lankhorst wrote:
>>> Op 15-11-12 04:52, Seung-Woo Kim schreef:
Increasing ref counts of both dma-buf and gem for imported dma-buf
come from gem makes mem
On 2012년 11월 20일 19:26, Maarten Lankhorst wrote:
> Op 20-11-12 02:03, 김승우 schreef:
>> Hi Maarten,
>>
>> On 2012년 11월 19일 19:27, Maarten Lankhorst wrote:
>>> Op 15-11-12 04:52, Seung-Woo Kim schreef:
Increasing ref counts of both dma-buf and gem for imported dma-buf
come from gem makes mem
Op 20-11-12 02:03, ??? schreef:
> Hi Maarten,
>
> On 2012? 11? 19? 19:27, Maarten Lankhorst wrote:
>> Op 15-11-12 04:52, Seung-Woo Kim schreef:
>>> Increasing ref counts of both dma-buf and gem for imported dma-buf
>>> come from gem makes memory leak. release function of dma-buf cannot
>>> be calle
Hi Maarten,
On 2012? 11? 19? 19:27, Maarten Lankhorst wrote:
> Op 15-11-12 04:52, Seung-Woo Kim schreef:
>> Increasing ref counts of both dma-buf and gem for imported dma-buf
>> come from gem makes memory leak. release function of dma-buf cannot
>> be called because f_count of dma-buf increased by
Op 20-11-12 02:03, 김승우 schreef:
> Hi Maarten,
>
> On 2012년 11월 19일 19:27, Maarten Lankhorst wrote:
>> Op 15-11-12 04:52, Seung-Woo Kim schreef:
>>> Increasing ref counts of both dma-buf and gem for imported dma-buf
>>> come from gem makes memory leak. release function of dma-buf cannot
>>> be calle
Hi All,
This patch has been tested with only Exynos driver so other maintainers may
need to test this.
Acked-by: Inki Dae
2012/11/15 Seung-Woo Kim
> Increasing ref counts of both dma-buf and gem for imported dma-buf
> come from gem makes memory leak. release function of dma-buf cannot
> be c
Hi Maarten,
On 2012년 11월 19일 19:27, Maarten Lankhorst wrote:
> Op 15-11-12 04:52, Seung-Woo Kim schreef:
>> Increasing ref counts of both dma-buf and gem for imported dma-buf
>> come from gem makes memory leak. release function of dma-buf cannot
>> be called because f_count of dma-buf increased by
Op 15-11-12 04:52, Seung-Woo Kim schreef:
> Increasing ref counts of both dma-buf and gem for imported dma-buf
> come from gem makes memory leak. release function of dma-buf cannot
> be called because f_count of dma-buf increased by importing gem and
> gem ref count cannot be decrease because of ex
Op 15-11-12 04:52, Seung-Woo Kim schreef:
> Increasing ref counts of both dma-buf and gem for imported dma-buf
> come from gem makes memory leak. release function of dma-buf cannot
> be called because f_count of dma-buf increased by importing gem and
> gem ref count cannot be decrease because of ex
Hi All,
This patch has been tested with only Exynos driver so other maintainers may
need to test this.
Acked-by: Inki Dae
2012/11/15 Seung-Woo Kim
> Increasing ref counts of both dma-buf and gem for imported dma-buf
> come from gem makes memory leak. release function of dma-buf cannot
> be c
Increasing ref counts of both dma-buf and gem for imported dma-buf
come from gem makes memory leak. release function of dma-buf cannot
be called because f_count of dma-buf increased by importing gem and
gem ref count cannot be decrease because of exported dma-buf.
So I add dma_buf_put() for import
Increasing ref counts of both dma-buf and gem for imported dma-buf
come from gem makes memory leak. release function of dma-buf cannot
be called because f_count of dma-buf increased by importing gem and
gem ref count cannot be decrease because of exported dma-buf.
So I add dma_buf_put() for import
Hi Jani,
Sorry for late reply.
On 2012? 09? 27? 22:43, Jani Nikula wrote:
> On Thu, 27 Sep 2012, Seung-Woo Kim wrote:
>> Increasing ref counts of both dma-buf and gem for imported dma-buf come from
>> gem
>> makes memory leak. release function of dma-buf cannot be called because
>> f_count
>>
Hi Jani,
Sorry for late reply.
On 2012년 09월 27일 22:43, Jani Nikula wrote:
> On Thu, 27 Sep 2012, Seung-Woo Kim wrote:
>> Increasing ref counts of both dma-buf and gem for imported dma-buf come from
>> gem
>> makes memory leak. release function of dma-buf cannot be called because
>> f_count
>>
On Thu, 27 Sep 2012, Seung-Woo Kim wrote:
> Increasing ref counts of both dma-buf and gem for imported dma-buf come from
> gem
> makes memory leak. release function of dma-buf cannot be called because
> f_count
> of dma-buf increased by importing gem and gem ref count cannot be decrease
> becaus
Hi Rob,
On 2012? 09? 27? 15:52, Rob Clark wrote:
> fwiw, I had a similar patch:
>
> https://patchwork.kernel.org/patch/1229161/
Yes, I already check your patch and even my patch's title is a bit from
your patch.
I thought locking issue blocks your patch, so I sent simple fixes on
current state.
Increasing ref counts of both dma-buf and gem for imported dma-buf come from gem
makes memory leak. release function of dma-buf cannot be called because f_count
of dma-buf increased by importing gem and gem ref count cannot be decrease
because of exported dma-buf.
So I add dma_buf_put() for import
On Thu, Sep 27, 2012 at 9:14 AM, ??? wrote:
> Hi Rob,
>
> On 2012? 09? 27? 15:52, Rob Clark wrote:
>> fwiw, I had a similar patch:
>>
>> https://patchwork.kernel.org/patch/1229161/
>
> Yes, I already check your patch and even my patch's title is a bit from
> your patch.
>
> I thought locking issue
fwiw, I had a similar patch:
https://patchwork.kernel.org/patch/1229161/
although it was on top of some locking fixes from Daniel (which I
think are also needed):
https://patchwork.kernel.org/patch/1227251/
although that seemed to cause/trigger some explosions which I think
still need to be deb
On Thu, 27 Sep 2012, Seung-Woo Kim wrote:
> Increasing ref counts of both dma-buf and gem for imported dma-buf come from
> gem
> makes memory leak. release function of dma-buf cannot be called because
> f_count
> of dma-buf increased by importing gem and gem ref count cannot be decrease
> becaus
On Thu, Sep 27, 2012 at 9:14 AM, 김승우 wrote:
> Hi Rob,
>
> On 2012년 09월 27일 15:52, Rob Clark wrote:
>> fwiw, I had a similar patch:
>>
>> https://patchwork.kernel.org/patch/1229161/
>
> Yes, I already check your patch and even my patch's title is a bit from
> your patch.
>
> I thought locking issue
Hi Rob,
On 2012년 09월 27일 15:52, Rob Clark wrote:
> fwiw, I had a similar patch:
>
> https://patchwork.kernel.org/patch/1229161/
Yes, I already check your patch and even my patch's title is a bit from
your patch.
I thought locking issue blocks your patch, so I sent simple fixes on
current state.
fwiw, I had a similar patch:
https://patchwork.kernel.org/patch/1229161/
although it was on top of some locking fixes from Daniel (which I
think are also needed):
https://patchwork.kernel.org/patch/1227251/
although that seemed to cause/trigger some explosions which I think
still need to be deb
Increasing ref counts of both dma-buf and gem for imported dma-buf come from gem
makes memory leak. release function of dma-buf cannot be called because f_count
of dma-buf increased by importing gem and gem ref count cannot be decrease
because of exported dma-buf.
So I add dma_buf_put() for import
30 matches
Mail list logo
