KASAN: Disable checking before triggering a panic

KASAN hooks will not generate reports if panicstr != NULL, but then
there is a window after the initial panic() call where another report
may be raised.  This can happen if a false positive occurs; to simplify
debugging of such problems, avoid recursing.

Sponsored by:	The FreeBSD Foundation

This commit is contained in:

Mark Johnston

2021-07-23 10:41:00 -04:00

parent 0dcef81de9

commit ea3fbe0707

1 changed files with 1 additions and 0 deletions

									
										sys/kern/subr_asan.c
									
		+1
		
												View File
												
					@@ -174,6 +174,7 @@ kasan_code_name(uint8_t code)

					#define	REPORT(f, ...) do {				\

					#define	REPORT(f, ...) do {				\

						if (panic_on_violation) {			\

						if (panic_on_violation) {			\

							kasan_enabled = false;			\

							panic(f, __VA_ARGS__);			\

							panic(f, __VA_ARGS__);			\

						} else {					\

						} else {					\

							struct stack st;			\

							struct stack st;			\