All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: WANG Rui <wangrui@loongson.cn>,
	Jianping Liu <frankljpliu@gmail.com>,
	peterz@infradead.org, mingo@redhat.com, namhyung@kernel.org,
	wangming01@loongson.cn, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jianping Liu <frankjpliu@tencent.com>
Subject: Re: [PATCH v2] perf annotate: Fix NULL pointer dereference in loongarch_call__parse
Date: Thu, 24 Sep 2026 19:52:36 +0200	[thread overview]
Message-ID: <arVjZFD8-amR8qFm@x2> (raw)
In-Reply-To: <CAP-5=fX37WjSviuitD8vintyY+EERwB-GMPpitarBqPFk49A3Q@mail.gmail.com>

On Tue, Sep 15, 2026 at 03:47:38PM -0700, Ian Rogers wrote:
> On Mon, Apr 27, 2026 at 8:53 PM WANG Rui <wangrui@loongson.cn> wrote:
> > On Thu, Apr 23, 2026 at 6:35 PM Jianping Liu <frankljpliu@gmail.com> wrote:
> > > Rather than aborting parse with -1 (which would clear dl->ins.ops and
> > > lose the is_call attribute, preventing the TUI from drawing branch
> > > arrows and navigating the call), follow the same pattern as the generic
> > > call__parse() in util/disasm.c: when the symbol name is absent, jump to
> > > the address-based symbol lookup so that ops->target.sym can still be
> > > resolved via maps__find_ams() using the already-parsed target address.
> > > This preserves is_call semantics and keeps TUI navigation working.

> > > - Link to v1: https://lore.kernel.org/all/20260423053102.3717015-1-frankljpliu@gmail.com/

> > > Fixes: 4ca0d340ce20 ("perf annotate: Fix instruction association and parsing for LoongArch")
> > > Signed-off-by: Jianping Liu <frankjpliu@tencent.com>
> > > Reviewed-by: Ming Wang <wangming01@loongson.cn>

> > Tested-by: WANG Rui <wangrui@loongson.cn>
 
> Acked-by: Ian Rogers <irogers@google.com>

Thanks, applied to perf-tools-next, for v7.4.

- Arnaldo

      reply	other threads:[~2026-09-24 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 10:35 [PATCH v2] perf annotate: Fix NULL pointer dereference in loongarch_call__parse Jianping Liu
2026-04-28  3:50 ` WANG Rui
2026-09-15 22:47   ` Ian Rogers
2026-09-24 17:52     ` Arnaldo Carvalho de Melo [this message]

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=arVjZFD8-amR8qFm@x2 \
    --to=acme@kernel.org \
    --cc=frankjpliu@tencent.com \
    --cc=frankljpliu@gmail.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=wangming01@loongson.cn \
    --cc=wangrui@loongson.cn \
    /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.