* [PATCH] objtool: Improve rate-limiting for missing __noreturn warnings
@ 2023-06-08 16:23 Josh Poimboeuf
2023-06-08 20:54 ` Josh Poimboeuf
0 siblings, 1 reply; 2+ messages in thread
From: Josh Poimboeuf @ 2023-06-08 16:23 UTC (permalink / raw)
To: x86; +Cc: linux-kernel, Peter Zijlstra, Miroslav Benes
If a function with a lot of call sites is missing __noreturn, it could
result in a lot of duplicate warnings (one for each call site).
Each call site's function is already rate-limited to one warning per
function via WARN_INSN(). Do the same for the callee (the "missing
__noreturn" function itself).
Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
---
tools/objtool/check.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/tools/objtool/check.c b/tools/objtool/check.c
index 8936a05f0e5a..bb2ed34cb90e 100644
--- a/tools/objtool/check.c
+++ b/tools/objtool/check.c
@@ -4507,9 +4507,13 @@ static int validate_reachable_instructions(struct objtool_file *file)
if (prev_insn && prev_insn->dead_end) {
call_dest = insn_call_dest(prev_insn);
if (call_dest && !ignore_noreturn_call(prev_insn)) {
- WARN_INSN(insn, "%s() is missing a __noreturn annotation",
- call_dest->name);
- warnings++;
+ if (!call_dest->warned) {
+ WARN_INSN(insn, "%s() is missing a __noreturn annotation",
+ call_dest->name);
+ warnings++;
+ call_dest->warned = 1;
+ }
+
continue;
}
}
--
2.40.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] objtool: Improve rate-limiting for missing __noreturn warnings
2023-06-08 16:23 [PATCH] objtool: Improve rate-limiting for missing __noreturn warnings Josh Poimboeuf
@ 2023-06-08 20:54 ` Josh Poimboeuf
0 siblings, 0 replies; 2+ messages in thread
From: Josh Poimboeuf @ 2023-06-08 20:54 UTC (permalink / raw)
To: x86; +Cc: linux-kernel, Peter Zijlstra, Miroslav Benes
On Thu, Jun 08, 2023 at 09:23:32AM -0700, Josh Poimboeuf wrote:
> If a function with a lot of call sites is missing __noreturn, it could
> result in a lot of duplicate warnings (one for each call site).
>
> Each call site's function is already rate-limited to one warning per
> function via WARN_INSN(). Do the same for the callee (the "missing
> __noreturn" function itself).
>
> Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
> ---
> tools/objtool/check.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/tools/objtool/check.c b/tools/objtool/check.c
> index 8936a05f0e5a..bb2ed34cb90e 100644
> --- a/tools/objtool/check.c
> +++ b/tools/objtool/check.c
> @@ -4507,9 +4507,13 @@ static int validate_reachable_instructions(struct objtool_file *file)
> if (prev_insn && prev_insn->dead_end) {
> call_dest = insn_call_dest(prev_insn);
> if (call_dest && !ignore_noreturn_call(prev_insn)) {
> - WARN_INSN(insn, "%s() is missing a __noreturn annotation",
> - call_dest->name);
> - warnings++;
> + if (!call_dest->warned) {
> + WARN_INSN(insn, "%s() is missing a __noreturn annotation",
> + call_dest->name);
> + warnings++;
> + call_dest->warned = 1;
> + }
> +
NAK - this spits out a bunch of unreachables, will need to tweak it a
bit.
--
Josh
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-06-08 20:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-08 16:23 [PATCH] objtool: Improve rate-limiting for missing __noreturn warnings Josh Poimboeuf
2023-06-08 20:54 ` Josh Poimboeuf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®