linux-kernel - Re: [for-next][PATCH 15/21] ftrace/kprobe: Show the maxactive number on kprobe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20200331131124.5C1ED20784@mail.kernel.org>
Date:   Tue, 31 Mar 2020 13:11:23 +0000
From:   Sasha Levin <sashal@...nel.org>
To:     linux-kernel@...r.kernel.org
Cc:     stable@...r.kernel.org
Subject: Re: [for-next][PATCH 15/21] ftrace/kprobe: Show the maxactive number on kprobe_events

Hi

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag
fixing commit: 696ced4fb1d7 ("tracing/kprobes: expose maxactive for kretprobe in kprobe_events").

The bot has tested the following trees: v5.5.13, v5.4.28, v4.19.113, v4.14.174.

v5.5.13: Build OK!
v5.4.28: Build OK!
v4.19.113: Failed to apply! Possible dependencies:
    533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
    56de76305279 ("tracing: probeevent: Cleanup print argument functions")
    60c2e0cebfd0 ("tracing: probeevent: Add symbol type")
    6212dd29683e ("tracing/kprobes: Use dyn_event framework for kprobe events")
    a1303af5d79e ("tracing: probeevent: Add $argN for accessing function args")
    b55ce203a8f3 ("tracing/probe: Add probe event name and group name accesses APIs")
    f451bc89d835 ("tracing: probeevent: Unify fetch type tables")

v4.14.174: Failed to apply! Possible dependencies:
    0b4c6841fee0 ("bpf: use the same condition in perf event set/free bpf handler")
    43fa87f7deed ("perf/core: Fix another perf,trace,cpuhp lock inversion")
    45408c4f9250 ("tracing: kprobes: Prohibit probing on notrace function")
    4bebdc7a85aa ("bpf: add helper bpf_perf_prog_read_value")
    533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
    60c2e0cebfd0 ("tracing: probeevent: Add symbol type")
    6212dd29683e ("tracing/kprobes: Use dyn_event framework for kprobe events")
    908432ca84fc ("bpf: add helper bpf_perf_event_read_value for perf event array map")
    97562633bcba ("bpf: perf event change needed for subsequent bpf helpers")
    9802d86585db ("bpf: add a bpf_override_function helper")
    a1303af5d79e ("tracing: probeevent: Add $argN for accessing function args")
    b4da3340eae2 ("tracing/kprobe: bpf: Check error injectable event is on function entry")
    b55ce203a8f3 ("tracing/probe: Add probe event name and group name accesses APIs")
    d899926f552b ("selftest/ftrace: Move kprobe selftest function to separate compile unit")
    dd0bb688eaa2 ("bpf: add a bpf_override_function helper")
    de8f3a83b0a0 ("bpf: add meta pointer for direct access")
    e12f03d7031a ("perf/core: Implement the 'perf_kprobe' PMU")
    f3edacbd697f ("bpf: Revert bpf_overrid_function() helper changes.")
    f451bc89d835 ("tracing: probeevent: Unify fetch type tables")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha