mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Chartre <alexandre.chartre@oracle.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: alexandre.chartre@oracle.com, linux-kernel@vger.kernel.org,
	mingo@kernel.org, peterz@infradead.org
Subject: Re: [PATCH v4 11/28] objtool: Trace instruction state changes during function validation
Date: Mon, 17 Nov 2025 08:33:43 +0100	[thread overview]
Message-ID: <1a2677f0-0357-42d5-b233-af5db94bf81d@oracle.com> (raw)
In-Reply-To: <7tn66k5ssfk33hndz4ljljgsyqm26wruxla2dqphahxozjousj@laoidocw54q2>


On 11/14/25 22:21, Josh Poimboeuf wrote:
> On Thu, Nov 13, 2025 at 05:49:00PM +0100, Alexandre Chartre wrote:
>> +/*
>> + * Return the name of a register. Note that the same static buffer
>> + * is returned if the name is dynamically generated.
>> + */
>> +static const char *cfi_reg_name(unsigned int reg)
>> +{
>> +	static char rname_buffer[CFI_REG_NAME_MAXLEN];
>> +
>> +	switch (reg) {
>> +	case CFI_UNDEFINED:
>> +		return "<undefined>";
>> +	case CFI_CFA:
>> +		return "cfa";
>> +	case CFI_SP_INDIRECT:
>> +		return "(sp)";
>> +	case CFI_BP_INDIRECT:
>> +		return "(bp)";
>> +	}
>> +
>> +	if (snprintf(rname_buffer, CFI_REG_NAME_MAXLEN, "r%d", reg) == 1)
>> +		return NULL;
> 
> An snprintf() error would either be -1 (error) or ">=
> CFI_REG_NAME_MAXLEN" (truncation).
> 
> Also maybe return "(error)" or so, so the caller doesn't need to check
> the return value.

Right, I will fix that.

>> +static void trace_cfi_reg(const char *prefix, int reg, const char *fmt,
>> +			  int base_prev, int offset_prev,
>> +			  int base_next, int offset_next)
>> +{
>> +	const char *rname;
>> +
>> +	if (base_prev == base_next && offset_prev == offset_next)
>> +		return;
>> +
>> +	if (prefix)
>> +		TRACE("%s:", prefix);
>> +
>> +	rname = cfi_reg_name(reg);
>> +
>> +	if (base_next == CFI_UNDEFINED) {
>> +		TRACE("%1$s=<undef> ", rname);
>> +	} else {
>> +		TRACE(fmt, rname,
>> +		      cfi_reg_name(base_next), offset_next);
> 
> Since cfi_reg_name() can reuse the same static local buffer, rname and
> cfi_reg_name(base_next) might point to the same string?
> 

Yes, good catch. I will fix.

Thanks,

alex.



  reply	other threads:[~2025-11-17  7:34 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 16:48 [PATCH v4 00/28] objtool: Function validation tracing Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 01/28] objtool: Move disassembly functions to a separated file Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 02/28] objtool: Create disassembly context Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 03/28] objtool: Disassemble code with libopcodes instead of running objdump Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 04/28] tool build: Remove annoying newline in build output Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 05/28] objtool: Print symbol during disassembly Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 06/28] objtool: Store instruction disassembly result Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 07/28] objtool: Disassemble instruction on warning or backtrace Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 08/28] objtool: Extract code to validate instruction from the validate branch loop Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 09/28] objtool: Record symbol name max length Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 10/28] objtool: Add option to trace function validation Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 11/28] objtool: Trace instruction state changes during " Alexandre Chartre
2025-11-14 21:21   ` Josh Poimboeuf
2025-11-17  7:33     ` Alexandre Chartre [this message]
2025-11-13 16:49 ` [PATCH v4 12/28] objtool: Improve register reporting " Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 13/28] objtool: Identify the different types of alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 14/28] objtool: Improve tracing of alternative instructions Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 15/28] objtool: Do not validate IBT for .return_sites and .call_sites Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 16/28] objtool: Add the --disas=<function-pattern> action Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 17/28] objtool: Print headers for alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 18/28] objtool: Disassemble group alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 19/28] objtool: Print addresses with alternative instructions Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 20/28] objtool: Disassemble exception table alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 21/28] objtool: Disassemble jump " Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 22/28] objtool: Fix address references in alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 23/28] objtool: Provide access to feature and flags of group alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 24/28] objtool: Function to get the name of a CPU feature Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 25/28] objtool: Improve naming of group alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 26/28] objtool: Get the destination name of a PV call Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 27/28] objtool: Improve the disassembly of the pv_ops call Alexandre Chartre
2025-11-15  1:34   ` kernel test robot
2025-11-17  7:37     ` Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 28/28] objtool: Print single line for alternatives with one instruction Alexandre Chartre
2025-11-13 19:55 ` [PATCH v4 00/28] objtool: Function validation tracing David Laight
2025-11-14  8:53   ` Alexandre Chartre
2025-11-14  1:48 ` Josh Poimboeuf
2025-11-14  9:56   ` Alexandre Chartre
2025-11-14 21:34     ` Josh Poimboeuf
2025-11-17  7:50       ` Alexandre Chartre
2025-11-17  9:42         ` David Laight
2025-11-17  9:47           ` Alexandre Chartre
2025-11-17 12:37             ` David Laight
2025-11-17 13:11               ` Alexandre Chartre
2025-11-17 22:09                 ` David Laight
2025-11-17 22:38                   ` Josh Poimboeuf
2025-11-18  9:58                     ` David Laight
2025-11-18  7:19                   ` Alexandre Chartre
2025-11-18  9:12                     ` Peter Zijlstra
2025-11-18 11:39                       ` Alexandre Chartre

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=1a2677f0-0357-42d5-b233-af5db94bf81d@oracle.com \
    --to=alexandre.chartre@oracle.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    /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®