Re: [PATCH v1 2/3] kernel/resource: make walk_mem_res() find all busy IORESOURCE_MEM resources

[David Hildenbrand]

On 23.03.21 12:08, Andy Shevchenko wrote:
> On Mon, Mar 22, 2021 at 05:01:59PM +0100, David Hildenbrand wrote:
> > It used to be true that we can have system RAM only on the first level
> > in the resourc tree. However, this is no longer holds for driver-managed
> > system RAM (i.e., dax/kmem and virtio-mem).
> >
> > The function walk_mem_res() only consideres the first level and is
> > used in arch/x86/mm/ioremap.c:__ioremap_check_mem() only. We currently
> > fail to identify System RAM added by dax/kmem and virtio-mem as
> > "IORES_MAP_SYSTEM_RAM", for example, allowing for remapping of such
> > "normal RAM" in __ioremap_caller().
>
> Here I dunno, but consider to add Fixes tag if it fixes known bad behaviour.

Haven't observed it in the wild. We can add the same fixes tags as to 
patch #1.

--
Thanks,

David / dhildenb