Re: [PATCH v2 1/3] drm/mm: Ensure that the entry is not NULL before extracting rb_node

On 23/02/2022 04:35, Kasireddy, Vivek wrote: Hi Tvrtko, On 18/02/2022 03:47, Kasireddy, Vivek wrote: Hi Tvrtko, On 17/02/2022 07:50, Vivek Kasireddy wrote: While looking for next holes suitable for an allocation, although, it is highly unlikely, make sure that the DECLARE_NEXT_HOLE_ADDR

RE: [PATCH v2 1/3] drm/mm: Ensure that the entry is not NULL before extracting rb_node

Hi Tvrtko, > > On 18/02/2022 03:47, Kasireddy, Vivek wrote: > > Hi Tvrtko, > > > >> > >> On 17/02/2022 07:50, Vivek Kasireddy wrote: > >>> While looking for next holes suitable for an allocation, although, > >>> it is highly unlikely, make sure that the DECLARE_NEXT_HOLE_ADDR > >>> macro is using

Re: [PATCH v2 1/3] drm/mm: Ensure that the entry is not NULL before extracting rb_node

On 18/02/2022 03:47, Kasireddy, Vivek wrote: Hi Tvrtko, On 17/02/2022 07:50, Vivek Kasireddy wrote: While looking for next holes suitable for an allocation, although, it is highly unlikely, make sure that the DECLARE_NEXT_HOLE_ADDR macro is using a valid node before it extracts the rb_node

RE: [PATCH v2 1/3] drm/mm: Ensure that the entry is not NULL before extracting rb_node

Hi Tvrtko, > > On 17/02/2022 07:50, Vivek Kasireddy wrote: > > While looking for next holes suitable for an allocation, although, > > it is highly unlikely, make sure that the DECLARE_NEXT_HOLE_ADDR > > macro is using a valid node before it extracts the rb_node from it. > > Was the need for this

Re: [PATCH v2 1/3] drm/mm: Ensure that the entry is not NULL before extracting rb_node

On 17/02/2022 07:50, Vivek Kasireddy wrote: While looking for next holes suitable for an allocation, although, it is highly unlikely, make sure that the DECLARE_NEXT_HOLE_ADDR macro is using a valid node before it extracts the rb_node from it. Was the need for this just a consequence of insuf