[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1644324666-15947-5-git-send-email-yangtiezhu@loongson.cn>
Date: Tue, 8 Feb 2022 20:51:05 +0800
From: Tiezhu Yang <yangtiezhu@...ngson.cn>
To: Baoquan He <bhe@...hat.com>, Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>,
Marco Elver <elver@...gle.com>,
Andrey Ryabinin <ryabinin.a.a@...il.com>
Cc: Xuefeng Li <lixuefeng@...ngson.cn>, kexec@...ts.infradead.org,
linux-doc@...r.kernel.org, kasan-dev@...glegroups.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: [PATCH v2 4/5] ubsan: no need to unset panic_on_warn in ubsan_epilogue()
panic_on_warn is unset inside panic(), so no need to unset it
before calling panic() in ubsan_epilogue().
Signed-off-by: Tiezhu Yang <yangtiezhu@...ngson.cn>
---
lib/ubsan.c | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/lib/ubsan.c b/lib/ubsan.c
index bdc380f..36bd75e 100644
--- a/lib/ubsan.c
+++ b/lib/ubsan.c
@@ -154,16 +154,8 @@ static void ubsan_epilogue(void)
current->in_ubsan--;
- if (panic_on_warn) {
- /*
- * This thread may hit another WARN() in the panic path.
- * Resetting this prevents additional WARN() from panicking the
- * system on this thread. Other threads are blocked by the
- * panic_mutex in panic().
- */
- panic_on_warn = 0;
+ if (panic_on_warn)
panic("panic_on_warn set ...\n");
- }
}
void __ubsan_handle_divrem_overflow(void *_data, void *lhs, void *rhs)
--
2.1.0
Powered by blists - more mailing lists