Linux Perf Users
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Namhyung Kim <namhyung@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>, "Ian Rogers" <irogers@google.com>,
	Clark Williams <williams@redhat.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCHES 0/5 v1] perf tools auxtrace hardening series
Date: Mon, 3 Aug 2026 21:46:38 +0300	[thread overview]
Message-ID: <dd4a6a5b-5abf-45e5-bb88-59d6e911123f@intel.com> (raw)
In-Reply-To: <am0vWwqDMib_NF6q@google.com>

On 01/08/2026 02:27, Namhyung Kim wrote:
> Hi Adrian,
> 
> On Mon, Jul 27, 2026 at 01:17:00PM -0300, Arnaldo Carvalho de Melo wrote:
>> Hi,
>>
>> 	Please consider applying,
>>
>> - Arnaldo
>>
>> Arnaldo Carvalho de Melo (5):
>>   perf thread-stack: Fix heap buffer overflow on branch stack wrap copy
>>   perf auxtrace: Fix queue grow overflow and old array leak
>>   perf intel-pt: Fix off-by-one in auxtrace_info minimum size check
>>   perf intel-bts: Fix off-by-one in auxtrace_info minimum size check
>>   perf arm-spe: Reject zero nr_cpu in metadata to prevent division by zero
> 
> Can you please review this series?

Certainly!

Other than the Fixes tag in "[PATCH 5/5] perf arm-spe: Reject zero
nr_cpu in metadata to prevent division by zero", for the series:

Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>

> 
> Thanks,
> Namhyung
> 
>>
>>  tools/perf/util/arm-spe.c      |  4 ++++
>>  tools/perf/util/auxtrace.c     | 15 ++++++++++-----
>>  tools/perf/util/intel-bts.c    |  2 +-
>>  tools/perf/util/intel-pt.c     |  2 +-
>>  tools/perf/util/thread-stack.c |  2 +-
>>  5 files changed, 17 insertions(+), 8 deletions(-)
>>
>> -- 
>> 2.55.0
>>


  reply	other threads:[~2026-08-03 18:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 16:17 [PATCHES 0/5 v1] perf tools auxtrace hardening series Arnaldo Carvalho de Melo
2026-07-27 16:17 ` [PATCH 1/5] perf thread-stack: Fix heap buffer overflow on branch stack wrap copy Arnaldo Carvalho de Melo
2026-07-27 16:32   ` sashiko-bot
2026-07-27 16:17 ` [PATCH 2/5] perf auxtrace: Fix queue grow overflow and old array leak Arnaldo Carvalho de Melo
2026-07-27 16:29   ` sashiko-bot
2026-07-27 16:17 ` [PATCH 3/5] perf intel-pt: Fix off-by-one in auxtrace_info minimum size check Arnaldo Carvalho de Melo
2026-07-27 16:35   ` sashiko-bot
2026-07-27 16:17 ` [PATCH 4/5] perf intel-bts: " Arnaldo Carvalho de Melo
2026-07-27 16:34   ` sashiko-bot
2026-07-27 16:17 ` [PATCH 5/5] perf arm-spe: Reject zero nr_cpu in metadata to prevent division by zero Arnaldo Carvalho de Melo
2026-07-27 16:32   ` sashiko-bot
2026-08-03 18:46   ` Adrian Hunter
2026-08-03 19:02     ` Arnaldo Carvalho de Melo
2026-08-03 19:41       ` Namhyung Kim
2026-07-27 16:31 ` [PATCHES 0/5 v1] perf tools auxtrace hardening series James Clark
2026-07-31 23:27 ` Namhyung Kim
2026-08-03 18:46   ` Adrian Hunter [this message]
2026-08-03 19:02     ` Arnaldo Carvalho de Melo
2026-08-04 17:04 ` Namhyung Kim

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=dd4a6a5b-5abf-45e5-bb88-59d6e911123f@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.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