Searched hist:"7749 dda24cf2b1f0a04d1de529cde03b6ca79867" (Results 1 – 5 of 5) sorted by relevance
| /optee_os/lib/libutils/isoc/arch/riscv/ |
| H A D | setjmp_rv.S | 7749dda24cf2b1f0a04d1de529cde03b6ca79867 Sun Jun 08 10:22:50 UTC 2025 Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de> core, libutils: unpoison stack on longjmp for ASan
Adds support for unpoisoning the stack when performing longjmp,
to ensure correct ASan behavior.
When a longjmp unwinds the stack, parts of the stack that were
poisoned during deeper calls may remain marked as inaccessible.
This can lead to false ASan reports after longjmp, as the new
frame reuses that memory.
To avoid this, a call to asan_handle_longjmp() is added to
setjmp_a64.S, which unpoisons the stack range between the current
SP and the old SP (saved during setjmp).
Signed-off-by: Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| /optee_os/lib/libutils/isoc/arch/arm/ |
| H A D | setjmp_a32.S | 7749dda24cf2b1f0a04d1de529cde03b6ca79867 Sun Jun 08 10:22:50 UTC 2025 Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de> core, libutils: unpoison stack on longjmp for ASan
Adds support for unpoisoning the stack when performing longjmp,
to ensure correct ASan behavior.
When a longjmp unwinds the stack, parts of the stack that were
poisoned during deeper calls may remain marked as inaccessible.
This can lead to false ASan reports after longjmp, as the new
frame reuses that memory.
To avoid this, a call to asan_handle_longjmp() is added to
setjmp_a64.S, which unpoisons the stack range between the current
SP and the old SP (saved during setjmp).
Signed-off-by: Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| H A D | setjmp_a64.S | 7749dda24cf2b1f0a04d1de529cde03b6ca79867 Sun Jun 08 10:22:50 UTC 2025 Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de> core, libutils: unpoison stack on longjmp for ASan
Adds support for unpoisoning the stack when performing longjmp,
to ensure correct ASan behavior.
When a longjmp unwinds the stack, parts of the stack that were
poisoned during deeper calls may remain marked as inaccessible.
This can lead to false ASan reports after longjmp, as the new
frame reuses that memory.
To avoid this, a call to asan_handle_longjmp() is added to
setjmp_a64.S, which unpoisons the stack range between the current
SP and the old SP (saved during setjmp).
Signed-off-by: Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| /optee_os/lib/libutils/isoc/include/ |
| H A D | setjmp.h | 7749dda24cf2b1f0a04d1de529cde03b6ca79867 Sun Jun 08 10:22:50 UTC 2025 Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de> core, libutils: unpoison stack on longjmp for ASan
Adds support for unpoisoning the stack when performing longjmp,
to ensure correct ASan behavior.
When a longjmp unwinds the stack, parts of the stack that were
poisoned during deeper calls may remain marked as inaccessible.
This can lead to false ASan reports after longjmp, as the new
frame reuses that memory.
To avoid this, a call to asan_handle_longjmp() is added to
setjmp_a64.S, which unpoisons the stack range between the current
SP and the old SP (saved during setjmp).
Signed-off-by: Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| /optee_os/core/kernel/ |
| H A D | asan.c | 7749dda24cf2b1f0a04d1de529cde03b6ca79867 Sun Jun 08 10:22:50 UTC 2025 Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de> core, libutils: unpoison stack on longjmp for ASan
Adds support for unpoisoning the stack when performing longjmp,
to ensure correct ASan behavior.
When a longjmp unwinds the stack, parts of the stack that were
poisoned during deeper calls may remain marked as inaccessible.
This can lead to false ASan reports after longjmp, as the new
frame reuses that memory.
To avoid this, a call to asan_handle_longjmp() is added to
setjmp_a64.S, which unpoisons the stack range between the current
SP and the old SP (saved during setjmp).
Signed-off-by: Aleksandr Iashchenko <aleksandr.iashchenko@linutronix.de>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|