[RESEND PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-23 Thread Mitchel Humpherys
There are certain client bugs (double unmap, for example) that can cause the handle->kmap_cnt (an unsigned int) to wrap around from zero. This causes problems when the handle is destroyed because we have: while (handle->kmap_cnt) ion_handle_kmap_put(handle); which takes a

Re: [PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-23 Thread Greg Kroah-Hartman
On Fri, May 23, 2014 at 11:34:59AM -0700, Mitchel Humpherys wrote: > ++greg-kh and de...@driverdev.osuosl.org > (my bad for missing you the first time around) What can I do with this? Please send patches to me in a format that I can actually apply them in... thanks, greg k-h -- To unsubscribe

Re: [PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-23 Thread Mitchel Humpherys
++greg-kh and de...@driverdev.osuosl.org (my bad for missing you the first time around) On Thu, May 22 2014 at 06:09:11 PM, Colin Cross wrote: > On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys > wrote: >> There are certain client bugs (double unmap, for example) that can cause >> the

Re: [PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-23 Thread Mitchel Humpherys
++greg-kh and de...@driverdev.osuosl.org (my bad for missing you the first time around) On Thu, May 22 2014 at 06:09:11 PM, Colin Cross ccr...@android.com wrote: On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys mitch...@codeaurora.org wrote: There are certain client bugs (double unmap, for

Re: [PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-23 Thread Greg Kroah-Hartman
On Fri, May 23, 2014 at 11:34:59AM -0700, Mitchel Humpherys wrote: ++greg-kh and de...@driverdev.osuosl.org (my bad for missing you the first time around) What can I do with this? Please send patches to me in a format that I can actually apply them in... thanks, greg k-h -- To unsubscribe

[RESEND PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-23 Thread Mitchel Humpherys
There are certain client bugs (double unmap, for example) that can cause the handle-kmap_cnt (an unsigned int) to wrap around from zero. This causes problems when the handle is destroyed because we have: while (handle-kmap_cnt) ion_handle_kmap_put(handle); which takes a

Re: [PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-22 Thread Colin Cross
On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys wrote: > There are certain client bugs (double unmap, for example) that can cause > the handle->kmap_cnt (an unsigned int) to wrap around from zero. This > causes problems when the handle is destroyed because we have: > > while

[PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-22 Thread Mitchel Humpherys
There are certain client bugs (double unmap, for example) that can cause the handle->kmap_cnt (an unsigned int) to wrap around from zero. This causes problems when the handle is destroyed because we have: while (handle->kmap_cnt) ion_handle_kmap_put(handle); which takes a

[PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-22 Thread Mitchel Humpherys
There are certain client bugs (double unmap, for example) that can cause the handle-kmap_cnt (an unsigned int) to wrap around from zero. This causes problems when the handle is destroyed because we have: while (handle-kmap_cnt) ion_handle_kmap_put(handle); which takes a

Re: [PATCH] staging: ion: WARN when the handle kmap_cnt is going to wrap around

2014-05-22 Thread Colin Cross
On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys mitch...@codeaurora.org wrote: There are certain client bugs (double unmap, for example) that can cause the handle-kmap_cnt (an unsigned int) to wrap around from zero. This causes problems when the handle is destroyed because we have: