[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230412140601.9308b871e38acb842c119478@linux-foundation.org>
Date: Wed, 12 Apr 2023 14:06:01 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: kernel test robot <lkp@...el.com>
Cc: Alexander Potapenko <glider@...gle.com>, llvm@...ts.linux.dev,
oe-kbuild-all@...ts.linux.dev, urezki@...il.com, hch@...radead.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, elver@...gle.com,
dvyukov@...gle.com, kasan-dev@...glegroups.com,
Dipanjan Das <mail.dipanjan.das@...il.com>
Subject: Re: [PATCH 1/2] mm: kmsan: handle alloc failures in
kmsan_vmap_pages_range_noflush()
On Thu, 13 Apr 2023 02:27:19 +0800 kernel test robot <lkp@...el.com> wrote:
> Hi Alexander,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on akpm-mm/mm-everything]
>
> >> include/linux/kmsan.h:291:1: error: non-void function does not return a value [-Werror,-Wreturn-type]
Thanks, I'll do this:
--- a/include/linux/kmsan.h~mm-kmsan-handle-alloc-failures-in-kmsan_ioremap_page_range-fix
+++ a/include/linux/kmsan.h
@@ -289,6 +289,7 @@ static inline int kmsan_vmap_pages_range
struct page **pages,
unsigned int page_shift)
{
+ return 0;
}
static inline void kmsan_vunmap_range_noflush(unsigned long start,
_
Powered by blists - more mailing lists