Re: [PATCH] mm: cma: improve pr_debug log in cma_release()

2020-11-27 Thread Vlastimil Babka
On 11/25/20 4:32 PM, Charan Teja Reddy wrote: It is required to print 'count' of pages, along with the pages, passed to cma_release to debug the cases of mismatched count value passed between cma_alloc() and cma_release() from a code path. As an example, consider the below scenario: 1) CMA pool

Re: [PATCH] mm: cma: improve pr_debug log in cma_release()

2020-11-25 Thread David Hildenbrand
On 25.11.20 16:32, Charan Teja Reddy wrote: > It is required to print 'count' of pages, along with the pages, passed > to cma_release to debug the cases of mismatched count value passed > between cma_alloc() and cma_release() from a code path. > > As an example, consider the below scenario: > 1)

Re: [PATCH] mm: cma: improve pr_debug log in cma_release()

2020-11-25 Thread Souptick Joarder
On Wed, Nov 25, 2020 at 9:02 PM Charan Teja Reddy wrote: > > It is required to print 'count' of pages, along with the pages, passed > to cma_release to debug the cases of mismatched count value passed > between cma_alloc() and cma_release() from a code path. > > As an example, consider the below

[PATCH] mm: cma: improve pr_debug log in cma_release()

2020-11-25 Thread Charan Teja Reddy
It is required to print 'count' of pages, along with the pages, passed to cma_release to debug the cases of mismatched count value passed between cma_alloc() and cma_release() from a code path. As an example, consider the below scenario: 1) CMA pool size is 4MB and 2) User doing the erroneous