Messages in this thread Patch in this message | | | From | andrey.konovalov@linux ... | Subject | [PATCH mm 05/11] kasan: update kasan_poison documentation comment | Date | Thu, 21 Dec 2023 21:04:47 +0100 |
| |
From: Andrey Konovalov <andreyknvl@google.com>
The comment for kasan_poison says that the size argument gets aligned by the function to KASAN_GRANULE_SIZE, which is wrong: the argument must be already aligned when it is passed to the function.
Remove the invalid part of the comment.
Signed-off-by: Andrey Konovalov <andreyknvl@google.com> --- mm/kasan/kasan.h | 2 -- 1 file changed, 2 deletions(-)
diff --git a/mm/kasan/kasan.h b/mm/kasan/kasan.h index 38af25b9c89c..1c34511090d7 100644 --- a/mm/kasan/kasan.h +++ b/mm/kasan/kasan.h @@ -513,8 +513,6 @@ static inline bool kasan_byte_accessible(const void *addr) * @size - range size, must be aligned to KASAN_GRANULE_SIZE * @value - value that's written to metadata for the range * @init - whether to initialize the memory range (only for hardware tag-based) - * - * The size gets aligned to KASAN_GRANULE_SIZE before marking the range. */ void kasan_poison(const void *addr, size_t size, u8 value, bool init); -- 2.25.1
| |