mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	chjohnst@mail.com, neelx@suse.com, sean@ashe.io,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH perf-tools-next v12 01/10] perf ftrace: Handle signals, non-blocking reads and pager exits in __cmd_ftrace()
Date: Wed, 4 Nov 2026 12:53:52 -0800	[thread overview]
Message-ID: <auubYIQRs560OPXk@google.com> (raw)
In-Reply-To: <gv2ojndchlo5yuwpqas554vgavuixfoenmaqsulvmqc65itz54@fjumgdv777w4>

On Sat, Oct 31, 2026 at 06:29:30PM -0400, Aaron Tomlin wrote:
> On Sat, Oct 31, 2026 at 12:12:32AM -0700, Namhyung Kim wrote:
> > On Sun, Oct 25, 2026 at 10:57:26PM -0400, Aaron Tomlin wrote:
> > > In __cmd_ftrace(), trace_fd is configured for non-blocking I/O via
> > > fcntl(trace_fd, F_SETFL, O_NONBLOCK) and polled using poll(). However,
> > > the polling loop previously treated any negative return code from poll()
> > > or read() as an unrecoverable failure.
> > > 
> > > If poll() or read() is interrupted by a non-fatal signal (i.e. SIGWINCH
> > > upon terminal resizing), errno is set to EINTR. Furthermore, read() on
> > > trace_pipe can return EAGAIN/EWOULDBLOCK even after poll() indicates
> > > POLLIN (for instance, under concurrent readers, spurious wakeups, or
> > > block-mode trace iterator options). In all such cases, breaking from the
> > > loop causes perf ftrace to terminate tracing prematurely.
> > > 
> > > Additionally, output errors on stdout (i.e. when a pager or consumer
> > > process exits, closing the downstream pipe) were ignored by fflush(),
> > > leaving __cmd_ftrace() polling indefinitely until the workload
> > > completes.
> > > 
> > > Resolve these concerns by retrying poll() upon receiving EINTR, retrying
> > > read() on EAGAIN, EWOULDBLOCK, and EINTR, and breaking on EOF (n == 0).
> > > Furthermore, detect stdout errors and broken pipes via fflush() and
> > > ferror() to exit immediately when the downstream output sink closes, and
> > > handle EINTR and ferror(stdout) cleanly in the subsequent buffer
> > > draining loop.
> > > 
> > > Fixes: d01f4e8db22c ("perf ftrace: Introduce new 'ftrace' tool")
> > > Cc: stable@vger.kernel.org
> > > Tested-by: Ian Rogers <irogers@google.com>
> > > Reviewed-by: Ian Rogers <irogers@google.com>
> > > Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>
> > 
> > Acked-by: Namhyung Kim <namhyung@kernel.org>

Applied to perf-tools-next, thanks!

Best regards
Namhyung


  reply	other threads:[~2026-11-04 20:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  2:57 [PATCH perf-tools-next v12 00/10] perf ftrace: Support inlined functions and display enhancements in function graph tracer Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 01/10] perf ftrace: Handle signals, non-blocking reads and pager exits in __cmd_ftrace() Aaron Tomlin
2026-10-31  7:12   ` Namhyung Kim
2026-10-31 22:29     ` Aaron Tomlin
2026-11-04 20:53       ` Namhyung Kim [this message]
2026-10-26  2:57 ` [PATCH perf-tools-next v12 02/10] perf ftrace: Optimise __cmd_ftrace() stack frame with strbuf streaming Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 03/10] perf ftrace: Support filtering return address comments Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 04/10] perf ftrace: Add basic task call stack management Aaron Tomlin
2026-10-31  7:05   ` Namhyung Kim
2026-10-31 22:27     ` Aaron Tomlin
2026-11-04  7:35       ` Namhyung Kim
2026-11-04 16:10         ` Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 05/10] perf ftrace: Support context switch tracking in function graph tracer Aaron Tomlin
2026-10-31 22:01   ` Namhyung Kim
2026-11-02  0:04     ` Aaron Tomlin
2026-11-04  7:42       ` Namhyung Kim
2026-11-04 16:45         ` Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 06/10] perf ftrace: Support display of inlined functions " Aaron Tomlin
2026-10-31  7:11   ` Namhyung Kim
2026-11-02 15:22     ` Aaron Tomlin
2026-10-31 23:33   ` Namhyung Kim
2026-11-02 19:20     ` Aaron Tomlin
2026-11-04  7:46       ` Namhyung Kim
2026-11-04 16:48         ` Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 07/10] perf symbol: Introduce vmlinux_path__find() helper Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 08/10] perf test: Add test for ftrace inline and task stack tracking Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 09/10] perf ftrace: Support omitting execution duration in function graph tracer Aaron Tomlin
2026-10-26  2:57 ` [PATCH perf-tools-next v12 10/10] perf ftrace: Filter extraneous functions " Aaron Tomlin

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=auubYIQRs560OPXk@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atomlin@atomlin.com \
    --cc=chjohnst@mail.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=neelx@suse.com \
    --cc=peterz@infradead.org \
    --cc=sean@ashe.io \
    /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®