From: patchwork-bot+netdevbpf@kernel.org
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
mpetlan@redhat.com, irogers@google.com,
alexander.shishkin@linux.intel.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, davemarchevsky@fb.com,
james.clark@arm.com, jolsa@kernel.org, john.fastabend@gmail.com,
kan.liang@linux.intel.com, kpsingh@kernel.org,
lv.ruyi@zte.com.cn, mark.rutland@arm.com, kafai@fb.com,
namhyung@kernel.org, netdev@vger.kernel.org,
peterz@infradead.org, quentin@isovalent.com,
songliubraving@fb.com, eranian@google.com,
zhengjun.xing@linux.intel.com, yhs@fb.com, acme@redhat.com,
sashal@kernel.org
Subject: Re: [PATCH 5.17 126/158] perf stat: Fix and validate CPU map inputs in synthetic PERF_RECORD_STAT events
Date: Wed, 25 May 2022 20:05:51 +0000 [thread overview]
Message-ID: <165350915170.15505.6185203070051218800.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220523165851.513336276@linuxfoundation.org>
Hello:
This patch was applied to netdev/net.git (master)
by Arnaldo Carvalho de Melo <acme@redhat.com>:
On Mon, 23 May 2022 19:04:43 +0200 you wrote:
> From: Ian Rogers <irogers@google.com>
>
> [ Upstream commit 92d579ea3279aa87392b862df5810f0a7e30fcc6 ]
>
> Stat events can come from disk and so need a degree of validation. They
> contain a CPU which needs looking up via CPU map to access a counter.
>
> [...]
Here is the summary with links:
- [5.17,126/158] perf stat: Fix and validate CPU map inputs in synthetic PERF_RECORD_STAT events
https://git.kernel.org/netdev/net/c/92d579ea3279
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-25 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220523165830.581652127@linuxfoundation.org>
2022-05-23 17:04 ` [PATCH 5.17 126/158] perf stat: Fix and validate CPU map inputs in synthetic PERF_RECORD_STAT events Greg Kroah-Hartman
2022-05-25 20:05 ` patchwork-bot+netdevbpf [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=165350915170.15505.6185203070051218800.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=eranian@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kan.liang@linux.intel.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.ruyi@zte.com.cn \
--cc=mark.rutland@arm.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=quentin@isovalent.com \
--cc=sashal@kernel.org \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=yhs@fb.com \
--cc=zhengjun.xing@linux.intel.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;
as well as URLs for NNTP newsgroup(s).