From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/3] perf-probe: Fix to check blacklist address correctly
Date: Sun, 26 Apr 2020 15:03:40 +0000 [thread overview]
Message-ID: <20200426150341.2AF472074F@mail.kernel.org> (raw)
In-Reply-To: <158763966411.30755.5882376357738273695.stgit@devnote2>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 9aaf5a5f479b ("perf probe: Check kprobes blacklist when adding new events").
The bot has tested the following trees: v5.6.7, v5.4.35, v4.19.118, v4.14.177, v4.9.220, v4.4.220.
v5.6.7: Build OK!
v5.4.35: Build OK!
v4.19.118: Build OK!
v4.14.177: Failed to apply! Possible dependencies:
Unable to calculate
v4.9.220: Failed to apply! Possible dependencies:
3da3ea7a8e20 ("perf probe: Factor out the ftrace README scanning")
7ab31d94bff9 ("perf kretprobes: Offset from reloc_sym if kernel supports it")
e491bc2f0dd9 ("perf probe: Generalize probe event file open routine")
v4.4.220: Failed to apply! Possible dependencies:
053a3989e12f ("perf report/top: Add --raw-trace option")
1c20b1d15473 ("perf probe: Show trace event definition")
2d8f0f18a5c3 ("perf tools: Add stat round user level event")
361459f163fa ("perf tools: Skip dynamic fields not defined for current event")
374fb9e362f6 ("perf tools: Add stat config user level event")
3938bad44ed2 ("perf tools: Remove needless 'extern' from function prototypes")
428aff82e92a ("perf probe: Ignore vmlinux buildid if offline kernel is given")
54430101d2af ("perf hists: Introduce hist_entry__filter()")
5f3339d2e83c ("perf thread_map: Add thread_map user level event")
60517d28fbd9 ("perf tools: Try to show pretty printed output for dynamic sort keys")
6640b6c227fc ("perf cpu_map: Add cpu_map user level event")
723928340c9d ("perf hist: Save raw_data/size for tracepoint events")
a34bb6a08d60 ("perf tools: Add 'trace' sort key")
b8f8eb84f483 ("perf tools: Remove misplaced __maybe_unused")
c7c2a5e40f17 ("perf tools: Add dynamic sort key for tracepoint events")
d7b617f51be4 ("perf tools: Pass perf_hpp_list all the way through setup_sort_list")
d80518c90bb2 ("perf tools: Add stat user level event")
fd36f3dd7933 ("perf hist: Pass struct sample to __hists__add_entry()")
ffe777254cce ("perf tools: Add event_update user level event")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-04-26 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 11:00 [PATCH 0/3] perf-probe: Fix __init function and blacklist checking Masami Hiramatsu
2020-04-23 11:01 ` [PATCH 1/3] perf-probe: Fix to check blacklist address correctly Masami Hiramatsu
2020-04-26 15:03 ` Sasha Levin [this message]
2020-05-06 16:44 ` Arnaldo Carvalho de Melo
2020-04-23 11:01 ` [PATCH 2/3] perf-probe: Check address correctness by map instead of _etext Masami Hiramatsu
2020-04-23 14:01 ` Arnaldo Carvalho de Melo
2020-04-23 11:01 ` [PATCH 3/3] perf-probe: Do not show the skipped events Masami Hiramatsu
2020-04-23 14:01 ` Arnaldo Carvalho de Melo
2020-04-23 23:33 ` Masami Hiramatsu
2020-04-24 13:08 ` Arnaldo Carvalho de Melo
2020-05-06 16:48 ` [PATCH 0/3] perf-probe: Fix __init function and blacklist checking 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=20200426150341.2AF472074F@mail.kernel.org \
--to=sashal@kernel.org \
--cc=mhiramat@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 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).