On Fri, Sep 16, 2022 at 8:19 PM kernel test robot <lkp(a)intel.com&gt; wrote: So if RISCV32 ... Think that passing a (void *) to virt_to_page() is a problem: I would think this is a problem with RISCV32. What has this arch done? This is a few lines up: dma_addr_t is a different size than (void *)? Given that the patch raising this problem looked like this: - return virt_to_page(paddr); + return virt_to_page((void *)paddr); I doubt that it has created a bug that wasn't there before. Passing a dma_addr_t to virt_to_page() might be wrong, but that is what the driver has been doing all the time. siw_pbl_get_buffer() claims to "Gets physical address backed by PBL element." Why is that even passed to virt_to_page() if it's no virtual address but a dma_addr_t to begin with? I certainly don't understand SIW, but this bug, if it is a bug (or a type and documentation bug) is clearly not new. Yours, Linus Walleij