mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: acme@kernel.org, adrian.hunter@intel.com, bvanassche@acm.org,
	elver@google.com, james.clark@linaro.org, jolsa@kernel.org,
	justinstitt@google.com, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, llvm@lists.linux.dev,
	mingo@redhat.com, morbo@google.com, nathan@kernel.org,
	ndesaulniers@google.com, peterz@infradead.org
Subject: Re: [PATCH v12 15/20] perf intel-tpebs: Fix race in tpebs_stop() and tpebs_cmd.out fd handling
Date: Wed, 11 Nov 2026 23:19:23 -0800	[thread overview]
Message-ID: <avVoe_hajXqJpfmq@google.com> (raw)
In-Reply-To: <20261111174213.3526604-16-irogers@google.com>

On Wed, Nov 11, 2026 at 09:42:07AM -0800, Ian Rogers wrote:
> In tpebs_stop(), read tpebs_reader_thread into a local variable before
> releasing tpebs_mtx to call pthread_join().
> 
> Transfer ownership of tpebs_cmd.out to __sample_reader() by passing it
> as the thread argument and setting tpebs_cmd.out = -1 in
> evsel__tpebs_open() so tpebs_stop() does not double-close the fd closed
> by perf_session__delete(). Also reset tpebs_cmd.pid = 0 and
> tpebs_cmd.out = -1 and return early if start_command() fails in
> evsel__tpebs_start_perf_record(), as start_command() closes the pipe
> internally and may leave cmd->pid = -1 on error.
> 
> Serialize tpebs_send_record_cmd() with teardown via tpebs_cmd_in_flight
> and tpebs_cmd_cond, newline-terminate control commands so consecutive
> writes cannot coalesce in evlist__ctlfd_recv(), check
> check_if_command_finished(&tpebs_cmd) under tpebs_mtx only when not
> stopping, ignore late samples in process_sample_event() once
> tpebs_stopping is set, and guard evsel__tpebs_open() against a
> concurrent tpebs_stop() with tpebs_gen, tpebs_enabled, and
> tpebs_stopping across closing the fds and finish_command().
> 
> Include <pthread.h>, <signal.h>, <stdint.h>, <stdlib.h>, <string.h>, and
> <unistd.h> explicitly.

I feel it's too verbose and not clear what's problem.  Please explain
the race and how it fixes the issue concisely.

Thanks,
Namhyung

  reply	other threads:[~2026-11-12  7:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 17:41 [PATCH v12 00/20] tools/perf: Adopt kernel compiler-context-analysis.h annotations Ian Rogers
2026-11-11 17:41 ` [PATCH v12 01/20] compiler-context-analysis: Avoid unused parameter warning in _context_unsafe_alias() Ian Rogers
2026-11-11 17:41 ` [PATCH v12 02/20] tools headers compiler: Synchronize compiler_types.h with the kernel sources Ian Rogers
2026-11-12  6:31   ` Namhyung Kim
2026-11-11 17:41 ` [PATCH v12 03/20] tools headers: Synchronize linux/compiler-context-analysis.h " Ian Rogers
2026-11-11 17:41 ` [PATCH v12 04/20] perf mutex: Use kernel style compiler-context-analysis.h annotations Ian Rogers
2026-11-11 17:41 ` [PATCH v12 05/20] perf build: Enable additional Clang thread-safety flags Ian Rogers
2026-11-11 17:41 ` [PATCH v12 06/20] perf comm: Add __guarded_by annotations to struct comm_strs Ian Rogers
2026-11-11 17:41 ` [PATCH v12 07/20] perf vdso: Fix unlocked __dsos__add() and race in __machine__addnew_vdso() Ian Rogers
2026-11-11 17:42 ` [PATCH v12 08/20] perf dsos: Skip BPF and OOL DSOs in dsos__find_kernel_dso() Ian Rogers
2026-11-12  6:44   ` Namhyung Kim
2026-11-11 17:42 ` [PATCH v12 09/20] perf dsos: Ensure DSOs in auxtrace, machine, and symbol are in dsos Ian Rogers
2026-11-11 17:42 ` [PATCH v12 10/20] perf dso: Pass dso_data to close_data_fd() and dso__list_del() Ian Rogers
2026-11-11 17:42 ` [PATCH v12 11/20] perf dso: Use DEFINE_MUTEX for dso__data_open_lock Ian Rogers
2026-11-11 17:42 ` [PATCH v12 12/20] perf dsos: Use read lock fast path in dsos__findnew_id() Ian Rogers
2026-11-12  6:53   ` Namhyung Kim
2026-11-11 17:42 ` [PATCH v12 13/20] perf dso: Expand context analysis annotations Ian Rogers
2026-11-11 17:42 ` [PATCH v12 14/20] perf thread: Expand context analysis annotations to threads and namespaces_lock Ian Rogers
2026-11-11 17:42 ` [PATCH v12 15/20] perf intel-tpebs: Fix race in tpebs_stop() and tpebs_cmd.out fd handling Ian Rogers
2026-11-12  7:19   ` Namhyung Kim [this message]
2026-11-11 17:42 ` [PATCH v12 16/20] perf intel-tpebs: Use DEFINE_MUTEX for tpebs_mtx Ian Rogers
2026-11-12  7:08   ` Namhyung Kim
2026-11-11 17:42 ` [PATCH v12 17/20] perf config, intel-tpebs, env: Add __guarded_by and __must_hold annotations Ian Rogers
2026-11-12  7:06   ` Namhyung Kim
2026-11-11 17:42 ` [PATCH v12 18/20] perf maps: Fix lock inversion in maps__load_first() Ian Rogers
2026-11-11 17:42 ` [PATCH v12 19/20] perf maps: Fix map index lookup fallback and removal Ian Rogers
2026-11-11 17:42 ` [PATCH v12 20/20] perf maps: Add context analysis annotations Ian Rogers

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=avVoe_hajXqJpfmq@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=bvanassche@acm.org \
    --cc=elver@google.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mingo@redhat.com \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --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®