From: Namhyung Kim <namhyung@kernel.org>
To: peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
linux-perf-users@vger.kernel.org, irogers@google.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
Yang Jihong <yangjihong1@huawei.com>,
adrian.hunter@intel.com, acme@kernel.org
Subject: Re: [PATCH 0/3] perf record: Fix segfault with '--timestamp-filename' option and pipe mode
Date: Mon, 22 Jan 2024 12:38:56 -0800 [thread overview]
Message-ID: <170595558520.377262.4040178885633671225.b4-ty@kernel.org> (raw)
In-Reply-To: <20240119040304.3708522-1-yangjihong1@huawei.com>
On Fri, 19 Jan 2024 04:03:01 +0000, Yang Jihong wrote:
> When perf record uses '--timestamp-filename' option and pipe mode,
> will occur segfault:
>
> # perf record --timestamp-filename -o- true 1>/dev/null
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Dump -.2024011813361681 ]
> perf: Segmentation fault
> Segmentation fault (core dumped)
>
> [...]
Applied to perf-tools-next, thanks!
Namhyung
prev parent reply other threads:[~2024-01-22 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 4:03 Yang Jihong
2024-01-19 4:03 ` [PATCH 1/3] perf record: Fix possible incorrect free in record__switch_output() Yang Jihong
2024-01-19 4:03 ` [PATCH 2/3] perf record: Check conflict between '--timestamp-filename' option and pipe mode before recording Yang Jihong
2024-01-19 4:03 ` [PATCH 3/3] perf data: Minor code style alignment cleanup Yang Jihong
2024-01-19 22:06 ` [PATCH 0/3] perf record: Fix segfault with '--timestamp-filename' option and pipe mode Namhyung Kim
2024-01-22 20:38 ` Namhyung Kim [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=170595558520.377262.4040178885633671225.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.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=peterz@infradead.org \
--cc=yangjihong1@huawei.com \
/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®