Re: [PATCH v2 1/3] kasan: use separate (un)poison implementation for integrated init
From: Catalin Marinas <catalin.marinas@arm.com>
Date: 2021-05-12 12:10:43
Also in:
linux-arm-kernel
On Tue, May 11, 2021 at 04:54:24PM -0700, Peter Collingbourne wrote:
quoted hunk ↗ jump to hunk
diff --git a/include/linux/kasan.h b/include/linux/kasan.h index b1678a61e6a7..e35fa301d3db 100644 --- a/include/linux/kasan.h +++ b/include/linux/kasan.h
[...]
quoted hunk ↗ jump to hunk
@@ -113,8 +113,30 @@ static inline bool kasan_has_integrated_init(void) return false; } +static __always_inline void kasan_alloc_pages(struct page *page, + unsigned int order, gfp_t flags) +{ + /* Only available for integrated init. */ + BUG(); +} + +static __always_inline void kasan_free_pages(struct page *page, + unsigned int order) +{ + /* Only available for integrated init. */ + BUG(); +}
Would these two work as BUILD_BUG()? -- Catalin