From: Namhyung Kim <namhyung@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Tamas Zsoldos <tamas.zsoldos@arm.com>
Subject: Re: [PATCH] perf session: Fix handling when buffer exceeds 2 GiB
Date: Fri, 15 Aug 2025 13:17:29 -0700 [thread overview]
Message-ID: <aJ-V2ZsYpN8RDQ3M@google.com> (raw)
In-Reply-To: <20250808-perf_fix_big_buffer_size-v1-1-45f45444a9a4@arm.com>
On Fri, Aug 08, 2025 at 02:24:40PM +0100, Leo Yan wrote:
> If a user specifies an AUX buffer larger than 2 GiB, the returned size
> may exceed 0x80000000. Since the err variable is defined as a signed
> 32-bit integer, such a value overflows and becomes negative.
>
> As a result, the perf record command reports an error:
>
> 0x146e8 [0x30]: failed to process type: 71 [Unknown error 183711232]
>
> Change the type of the err variable to a signed 64-bit integer to
> accommodate large buffer sizes correctly.
>
> Reported-by: Tamas Zsoldos <tamas.zsoldos@arm.com>
> Fixes: d5652d865ea7 ("perf session: Add ability to skip 4GiB or more")
> Signed-off-by: Leo Yan <leo.yan@arm.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
> ---
> tools/perf/util/session.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
> index 26ae078278cd67fc5894c01cbb44c4b8fa81321a..09af486c83e4ff82e74f17f3da08d3bc3989768b 100644
> --- a/tools/perf/util/session.c
> +++ b/tools/perf/util/session.c
> @@ -1402,7 +1402,7 @@ static s64 perf_session__process_user_event(struct perf_session *session,
> const struct perf_tool *tool = session->tool;
> struct perf_sample sample;
> int fd = perf_data__fd(session->data);
> - int err;
> + s64 err;
>
> perf_sample__init(&sample, /*all=*/true);
> if ((event->header.type != PERF_RECORD_COMPRESSED &&
>
> ---
> base-commit: 6235ce77749f45cac27f630337e2fdf04e8a6c73
> change-id: 20250808-perf_fix_big_buffer_size-e28f618df61c
>
> Best regards,
> --
> Leo Yan <leo.yan@arm.com>
>
next prev parent reply other threads:[~2025-08-15 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 13:24 Leo Yan
2025-08-15 20:17 ` Namhyung Kim [this message]
2025-09-17 17:41 ` Arnaldo Carvalho de Melo
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=aJ-V2ZsYpN8RDQ3M@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=tamas.zsoldos@arm.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®