mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: xur@google.com
To: Josh Poimboeuf <jpoimboe@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>, Rong Xu <xur@google.com>
Cc: linux-kernel@vger.kernel.org,
	Sriraman Tallam <tmsriram@google.com>,
	 Han Shen <shenhan@google.com>,
	Krzysztof Pszeniczny <kpszeniczny@google.com>
Subject: [PATCH v3 1/2] objtool: Fix the check for dead_end function with multiple sibling calls
Date: Wed, 19 Nov 2025 17:32:43 +0000	[thread overview]
Message-ID: <20251119173243.1625930-1-xur@google.com> (raw)

From: Rong Xu <xur@google.com>

If a function has multiple sibling calls, the dead_end check should
only return true if all sibling call targets are also dead_end
functions.

Signed-off-by: Rong Xu <xur@google.com>
Reviewed-by: Sriraman Tallam <tmsriram@google.com>
Reviewed-by: Han Shen <shenhan@google.com>
Reviewed-by: Krzysztof Pszeniczny <kpszeniczny@google.com>
Acked-by: Josh Poimboeuf <jpoimboe@kernel.org>

ChangedLog:
v3: Fix the typos in the commit message. (From Josh Poimboeuf).
    Drop the other patch (split funciton) as Josh has a better fix.
    Add Acked-by from Josh.
---
 tools/objtool/check.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/tools/objtool/check.c b/tools/objtool/check.c
index 9004fbc067693..c2ee3c3a84a62 100644
--- a/tools/objtool/check.c
+++ b/tools/objtool/check.c
@@ -314,7 +314,13 @@ static bool __dead_end_function(struct objtool_file *file, struct symbol *func,
 				return false;
 			}
 
-			return __dead_end_function(file, insn_func(dest), recursion+1);
+			/*
+			 * A function can have multiple sibling calls. All of
+			 * them need to be dead ends for the function to be a
+			 * dead end too.
+			 */
+			if (!__dead_end_function(file, insn_func(dest), recursion+1))
+				return false;
 		}
 	}
 

base-commit: 8b690556d8fe074b4f9835075050fba3fb180e93
-- 
2.52.0.rc1.455.g30608eb744-goog


                 reply	other threads:[~2025-11-19 17:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251119173243.1625930-1-xur@google.com \
    --to=xur@google.com \
    --cc=jpoimboe@kernel.org \
    --cc=kpszeniczny@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=shenhan@google.com \
    --cc=tmsriram@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®