From: Jiri Olsa <olsajiri@gmail.com>
To: Denis Nikitin <denik@chromium.org>
Cc: acme@kernel.org, linux-perf-users@vger.kernel.org,
jolsa@kernel.org, alexey.budankov@linux.intel.com,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
james.clark@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf session: Remap buf if there is no space for event
Date: Thu, 31 Mar 2022 13:44:43 +0200 [thread overview]
Message-ID: <YkWUK+1padnj2JB4@krava> (raw)
In-Reply-To: <20220330031130.2152327-1-denik@chromium.org>
On Tue, Mar 29, 2022 at 08:11:30PM -0700, Denis Nikitin wrote:
> If a perf event doesn't fit into remaining buffer space return NULL to
> remap buf and fetch the event again.
> Keep the logic to error out on inadequate input from fuzzing.
>
> This fixes perf failing on ChromeOS (with 32b userspace):
>
> $ perf report -v -i perf.data
> ...
> prefetch_event: head=0x1fffff8 event->header_size=0x30, mmap_size=0x2000000: fuzzed or compressed perf.data?
> Error:
> failed to process sample
>
> Fixes: 57fc032ad643 ("perf session: Avoid infinite loop when seeing invalid header.size")
> Signed-off-by: Denis Nikitin <denik@chromium.org>
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
> ---
> tools/perf/util/session.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
> index 3b8dfe603e50..45a30040ec8d 100644
> --- a/tools/perf/util/session.c
> +++ b/tools/perf/util/session.c
> @@ -2095,6 +2095,7 @@ prefetch_event(char *buf, u64 head, size_t mmap_size,
> bool needs_swap, union perf_event *error)
> {
> union perf_event *event;
> + u16 event_size;
>
> /*
> * Ensure we have enough space remaining to read
> @@ -2107,15 +2108,23 @@ prefetch_event(char *buf, u64 head, size_t mmap_size,
> if (needs_swap)
> perf_event_header__bswap(&event->header);
>
> - if (head + event->header.size <= mmap_size)
> + event_size = event->header.size;
> + if (head + event_size <= mmap_size)
> return event;
>
> /* We're not fetching the event so swap back again */
> if (needs_swap)
> perf_event_header__bswap(&event->header);
>
> - pr_debug("%s: head=%#" PRIx64 " event->header_size=%#x, mmap_size=%#zx:"
> - " fuzzed or compressed perf.data?\n",__func__, head, event->header.size, mmap_size);
> + /* Check if the event fits into the next mmapped buf. */
> + if (event_size <= mmap_size - head % page_size) {
> + /* Remap buf and fetch again. */
> + return NULL;
> + }
> +
> + /* Invalid input. Event size should never exceed mmap_size. */
> + pr_debug("%s: head=%#" PRIx64 " event->header.size=%#x, mmap_size=%#zx:"
> + " fuzzed or compressed perf.data?\n", __func__, head, event_size, mmap_size);
>
> return error;
> }
> --
> 2.35.1.1021.g381101b075-goog
>
next prev parent reply other threads:[~2022-03-31 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 3:11 [PATCH] perf session: Remap buf if there is no space for event Denis Nikitin
2022-03-31 11:44 ` Jiri Olsa [this message]
2022-04-09 15:30 ` Arnaldo Carvalho de Melo
2022-03-31 14:20 ` James Clark
2022-04-01 5:47 ` Denis Nikitin
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=YkWUK+1padnj2JB4@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=denik@chromium.org \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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.