The quilt patch titled Subject: kasan: update kasan_poison documentation comment has been removed from the -mm tree. Its filename was kasan-update-kasan_poison-documentation-comment.patch This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm ------------------------------------------------------ From: Andrey Konovalov <andreyknvl@xxxxxxxxxx> Subject: kasan: update kasan_poison documentation comment Date: Thu, 21 Dec 2023 21:04:47 +0100 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. Link: https://lkml.kernel.org/r/992a302542059fc40d86ea560eac413ecb31b6a1.1703188911.git.andreyknvl@xxxxxxxxxx Signed-off-by: Andrey Konovalov <andreyknvl@xxxxxxxxxx> Cc: Alexander Potapenko <glider@xxxxxxxxxx> Cc: Andrey Ryabinin <ryabinin.a.a@xxxxxxxxx> Cc: Dmitry Vyukov <dvyukov@xxxxxxxxxx> Cc: Marco Elver <elver@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/kasan/kasan.h | 2 -- 1 file changed, 2 deletions(-) --- a/mm/kasan/kasan.h~kasan-update-kasan_poison-documentation-comment +++ a/mm/kasan/kasan.h @@ -513,8 +513,6 @@ static inline bool kasan_byte_accessible * @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); _ Patches currently in -mm which might be from andreyknvl@xxxxxxxxxx are kasan-stop-leaking-stack-trace-handles.patch