public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Changbin Du <changbin.du@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Changbin Du <changbin.du@gmail.com>,
	rostedt@goodmis.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] kprobe: safely access memory specified by userspace
Date: Tue, 29 Jan 2019 03:07:52 +0000	[thread overview]
Message-ID: <20190129030750.3ihicycu2afvjnnk@mail.google.com> (raw)
In-Reply-To: <20190129003521.3327B2183F@mail.kernel.org>

Hi,
Please hold until Steven returned from Linux Conf Au. Thanks!

On Tue, Jan 29, 2019 at 12:35:20AM +0000, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
> 
> The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96, v4.9.153, v4.4.172, v3.18.133.
> 
> v4.20.5: Build OK!
> v4.19.18: Failed to apply! Possible dependencies:
>     533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
>     56de76305279 ("tracing: probeevent: Cleanup print argument functions")
>     9178412ddf5a ("tracing: probeevent: Return consumed bytes of dynamic area")
> 
> v4.14.96: Failed to apply! Possible dependencies:
>     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")
>     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")
>     b4da3340eae2 ("tracing/kprobe: bpf: Check error injectable event is on function entry")
>     cd86d1fd2102 ("bpf: Adding helper function bpf_getsockops")
>     dd0bb688eaa2 ("bpf: add a bpf_override_function helper")
>     de8f3a83b0a0 ("bpf: add meta pointer for direct access")
>     f3edacbd697f ("bpf: Revert bpf_overrid_function() helper changes.")
> 
> v4.9.153: Failed to apply! Possible dependencies:
>     17bedab27231 ("bpf: xdp: Allow head adjustment in XDP prog")
>     1d9995771fcb ("s390: update defconfigs")
>     23a4e389bdc7 ("nfp: create separate define for max number of vectors")
>     416db5c1e448 ("nfp: remove support for nfp3200")
>     45408c4f9250 ("tracing: kprobes: Prohibit probing on notrace function")
>     533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
>     67f8b1dcb9ee ("net/mlx4_en: Refactor the XDP forwarding rings scheme")
>     68453c7a8973 ("nfp: centralize runtime reconfiguration logic")
>     6b0b7551428e ("perf/core: Rename CONFIG_[UK]PROBE_EVENT to CONFIG_[UK]PROBE_EVENTS")
>     7ff5c83a1deb ("nfp: simplify nfp_net_poll()")
>     9802d86585db ("bpf: add a bpf_override_function helper")
>     a4b562bb8ebd ("nfp: use unsigned int for vector/ring counts")
>     b4da3340eae2 ("tracing/kprobe: bpf: Check error injectable event is on function entry")
>     bf187ea01b07 ("nfp: centralize the buffer size calculation")
>     cbeaf7aa733a ("nfp: bring back support for different ring counts")
>     ccc109b8ed24 ("net/mlx4_en: Add TX_XDP for CQ types")
>     dd0bb688eaa2 ("bpf: add a bpf_override_function helper")
>     e390b55d5aef ("bpf: make bpf_xdp_adjust_head support mandatory")
>     ecd63a0217d5 ("nfp: add XDP support in the driver")
>     f18f97ac43d7 ("tracing/kprobes: Add a helper method to return number of probe hits")
>     f3edacbd697f ("bpf: Revert bpf_overrid_function() helper changes.")
> 
> v4.4.172: Failed to apply! Possible dependencies:
>     1d9995771fcb ("s390: update defconfigs")
>     45408c4f9250 ("tracing: kprobes: Prohibit probing on notrace function")
>     533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
>     6b0b7551428e ("perf/core: Rename CONFIG_[UK]PROBE_EVENT to CONFIG_[UK]PROBE_EVENTS")
>     6e127efeeae5 ("s390/config: make the vector optimized crc function builtin")
>     a086171ad886 ("s390: Updated kernel config files")
>     cb14def6a9ca ("s390/configs: update default configurations")
>     e9bc15f28e5f ("s390/config: update default configuration")
>     fdcebf6f18ee ("s390/config: Enable config options for Docker")
> 
> v3.18.133: Failed to apply! Possible dependencies:
>     1a6877b9c0c2 ("lib: introduce strncpy_from_unsafe()")
>     34c0dad75229 ("s390/hypfs: Add diagnose 0c support")
>     45408c4f9250 ("tracing: kprobes: Prohibit probing on notrace function")
>     533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
>     5a79859ae0f3 ("s390: remove 31 bit support")
>     5c6497c50f8d ("s390/jump label: add sanity checks")
>     6b0b7551428e ("perf/core: Rename CONFIG_[UK]PROBE_EVENT to CONFIG_[UK]PROBE_EVENTS")
>     8461b63ca01d ("s390: translate cputime magic constants to macros")
>     a763bc8b656d ("s390/numa: enable support in s390 configs")
>     c07af4f1ce41 ("mm: add missing __PAGETABLE_{PUD,PMD}_FOLDED defines")
>     c933146a5e41 ("s390/ftrace,kprobes: allow to patch first instruction")
>     d5caa4dbf9bd ("s390/jump label: use different nop instruction")
>     e9bc15f28e5f ("s390/config: update default configuration")
>     f8b2dcbd9e6d ("s390: add z13 code generation support")
> 
> 
> How should we proceed with this patch?
> 
> --
> Thanks,
> Sasha

-- 
Cheers,
Changbin Du

  parent reply	other threads:[~2019-01-29  3:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 15:10 [PATCH] kprobe: safely access memory specified by userspace Changbin Du
     [not found] ` <20190129003521.3327B2183F@mail.kernel.org>
2019-01-29  3:07   ` Changbin Du [this message]
2019-02-13 14:36 ` Changbin Du
2019-02-13 15:41   ` Steven Rostedt
2019-02-14  0:05     ` Changbin Du
2019-02-14 13:04       ` Steven Rostedt
2019-02-14 14:10         ` Changbin Du
2019-02-14 14:44           ` Steven Rostedt

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=20190129030750.3ihicycu2afvjnnk@mail.google.com \
    --to=changbin.du@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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