From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, Song Liu <song@kernel.org>,
bpf@vger.kernel.org
Subject: Re: [PATCH] perf lock contention: Add a missing NULL check
Date: Tue, 2 Apr 2024 16:45:08 -0300 [thread overview]
Message-ID: <ZgxgRJdFlwfESwKF@x1> (raw)
In-Reply-To: <20240402184543.898923-1-namhyung@kernel.org>
On Tue, Apr 02, 2024 at 11:45:43AM -0700, Namhyung Kim wrote:
> I got a report for a failure in BPF verifier on a recent kernel with
> perf lock contention command. It checks task->sighand->siglock without
> checking if sighand is NULL or not. Let's add one.
>
> ; if (&curr->sighand->siglock == (void *)lock)
> 265: (79) r1 = *(u64 *)(r0 +2624) ; frame1: R0_w=trusted_ptr_task_struct(off=0,imm=0) R1_w=rcu_ptr_or_null_sighand_struct(off=0,imm=0)
> 266: (b7) r2 = 0 ; frame1: R2_w=0
> 267: (0f) r1 += r2
> R1 pointer arithmetic on rcu_ptr_or_null_ prohibited, null-check it first
> processed 164 insns (limit 1000000) max_states_per_insn 1 total_states 15 peak_states 15 mark_read 5
> -- END PROG LOAD LOG --
> libbpf: prog 'contention_end': failed to load: -13
> libbpf: failed to load object 'lock_contention_bpf'
> libbpf: failed to load BPF skeleton 'lock_contention_bpf': -13
> Failed to load lock-contention BPF skeleton
> lock contention BPF setup failed
> lock contention did not detect any lock contention
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Are you going to have this merged into perf-tools?
A Fixes: tag isn't perhaps needed as it worked in the past?
- Arnaldo
> ---
> tools/perf/util/bpf_skel/lock_contention.bpf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/bpf_skel/lock_contention.bpf.c b/tools/perf/util/bpf_skel/lock_contention.bpf.c
> index fb54bd38e7d0..4e5914d7eeaa 100644
> --- a/tools/perf/util/bpf_skel/lock_contention.bpf.c
> +++ b/tools/perf/util/bpf_skel/lock_contention.bpf.c
> @@ -305,7 +305,7 @@ static inline __u32 check_lock_type(__u64 lock, __u32 flags)
> break;
> case LCB_F_SPIN: /* spinlock */
> curr = bpf_get_current_task_btf();
> - if (&curr->sighand->siglock == (void *)lock)
> + if (curr->sighand && &curr->sighand->siglock == (void *)lock)
> return LCD_F_SIGHAND_LOCK;
> break;
> default:
> --
> 2.44.0.478.gd926399ef9-goog
next prev parent reply other threads:[~2024-04-02 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 18:45 [PATCH] perf lock contention: Add a missing NULL check Namhyung Kim
2024-04-02 18:49 ` Ian Rogers
2024-04-02 19:45 ` Arnaldo Carvalho de Melo [this message]
2024-04-02 20:42 ` Namhyung Kim
2024-04-02 21:37 ` Arnaldo Carvalho de Melo
2024-04-09 22:29 ` Namhyung Kim
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=ZgxgRJdFlwfESwKF@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=song@kernel.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 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.