All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: liujing <liujing@cmss.chinamobile.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf intel-pt: Fix undefined shift in intel_pt_bip()
Date: Thu, 03 Sep 2026 08:31:10 +0000	[thread overview]
Message-ID: <20260903083110.C416F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260903082128.4972-2-liujing@cmss.chinamobile.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch introduces a build failure by placing a variable declaration after a statement block, which violates the C90 compilation rules enforced in the perf tools build system.
--

commit 8a68d39b58963034d86457f673e830e359365de8
Author: Liu Jing <liujing@cmss.chinamobile.com>

perf intel-pt: Fix undefined shift in intel_pt_bip()

This commit aims to fix an undefined shift behavior in intel_pt_bip() by
moving the bounds check before the shift and using an unsigned shift operation.

> diff --git a/tools/perf/util/intel-pt-decoder/intel-pt-decoder.c b/tools/perf/util/intel-pt-decoder/intel-pt-decoder.c
> index e733f6b1f7ac5..9abadd0d1c108 100644
> --- a/tools/perf/util/intel-pt-decoder/intel-pt-decoder.c
> +++ b/tools/perf/util/intel-pt-decoder/intel-pt-decoder.c
> @@ -2060,7 +2060,6 @@ static void intel_pt_bbp(struct intel_pt_decoder *decoder)
>  static void intel_pt_bip(struct intel_pt_decoder *decoder)
>  {
>  	uint32_t id = decoder->packet.count;
> -	uint32_t bit = 1 << id;
>  	int pos = decoder->blk_type_pos;
>  
>  	if (pos < 0 || id >= INTEL_PT_BLK_ITEM_ID_CNT) {
> @@ -2068,6 +2067,7 @@ static void intel_pt_bip(struct intel_pt_decoder *decoder)
>  			     id, decoder->blk_type);
>  		return;
>  	}
> +	uint32_t bit = 1U << id;

[Severity: Low]
Will this cause a build failure? It looks like the declaration of the bit
variable is now placed after an if statement block within intel_pt_bip().

The perf tools build system enables -Wdeclaration-after-statement and promotes
it to an error. Could this be fixed by separating the declaration and
initialization, like declaring uint32_t bit; at the top of the function and
then assigning it after the bounds check?

>  
>  	if (decoder->state.items.mask[pos] & bit) {
>  		intel_pt_log("WARNING: Duplicate block item %u type %d\n",

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260903082128.4972-2-liujing@cmss.chinamobile.com?part=1

  reply	other threads:[~2026-09-03  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  8:21 [PATCH] perf sched: Fix resource leak in enable_sched_schedstats() liujing
2026-09-03  8:21 ` [PATCH] perf intel-pt: Fix undefined shift in intel_pt_bip() liujing
2026-09-03  8:31   ` sashiko-bot [this message]
2026-09-08 20:58     ` Arnaldo Carvalho de Melo
2026-09-03  8:21 ` [PATCH] perf script: Fix unsigned comparison against zero in print_bstack_flags() liujing
2026-09-03  8:26   ` sashiko-bot
2026-09-03  8:21 ` [PATCH] perf arm: Fix memory leak in find_all_arm_spe_pmus() liujing
2026-09-03  8:31   ` sashiko-bot
2026-09-03  8:33 ` [PATCH] perf sched: Fix resource leak in enable_sched_schedstats() sashiko-bot

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=20260903083110.C416F1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=liujing@cmss.chinamobile.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.