Conversation

And merged! Over 60 patches, combined with a few clean-ups. Memory Tagging–based KASAN can now prevent malicious accesses to non-executable vmalloc allocations. git.kernel.org/pub/scm/linux/

Quote Tweet

Andrey Konovalov

@andreyknvl

Nov 30, 2021

Posted v1 of the patch series that adds vmalloc tagging support to Memory Tagging–based KASAN. This will prevent certain types of vmalloc-out-of-bounds bugs on MTE-enabled devices. lore.kernel.org/linux-mm/cover

Gustavo A. R. Silva 3x

@embeddedgus

Mar 26

Replying to

@andreyknvl

Hi! I wonder if they are related to the following warnings with -Wstringop-overflow enabled and GCC 11:

Gustavo A. R. Silva 3x

Replying to

and

lib/test_kasan.c:274:49: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] lib/test_kasan.c:194:63: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] lib/test_kasan.c:139:57: warning: writing 1 byte into a region of size 0

Gustavo A. R. Silva 3x

Replying to

and

lib/test_kasan.c:145:53: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] lib/test_kasan.c:760:19: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]

Andrey Konovalov

@andreyknvl

Replying to

@embeddedgus

These are not related to the vmalloc changes, but we do need more OPTIMIZER_HIDE_VAR annotations in the tests. There are patches on the list to address these, but looks like they haven't been picked up yet.

2:46 AM · Mar 26, 2022Twitter Web App

Likes