From: Song Liu <songliubraving@fb.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Peter Ziljstra <peterz@infradead.org>,
"Alexei Starovoitov" <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"Kernel Team" <Kernel-team@fb.com>,
john fastabend <john.fastabend@gmail.com>,
"KP Singh" <kpsingh@chromium.org>
Subject: Re: [PATCH v2 bpf-next 2/4] bpf: introduce helper bpf_get_task_stak()
Date: Fri, 26 Jun 2020 23:47:37 +0000 [thread overview]
Message-ID: <AD7AE0B3-94F9-4430-990C-85B9CF431EC7@fb.com> (raw)
In-Reply-To: <CAEf4BzaC1Dqn3PXBJmczPRaUmjKc7pcg6_mjyKymBek-sDKv7Q@mail.gmail.com>
> On Jun 26, 2020, at 3:51 PM, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>
> On Fri, Jun 26, 2020 at 3:45 PM Song Liu <songliubraving@fb.com> wrote:
>>
>>
>>
>>> On Jun 26, 2020, at 1:17 PM, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>>>
>>> On Thu, Jun 25, 2020 at 5:14 PM Song Liu <songliubraving@fb.com> wrote:
>>>>
>>>> Introduce helper bpf_get_task_stack(), which dumps stack trace of given
>>>> task. This is different to bpf_get_stack(), which gets stack track of
>>>> current task. One potential use case of bpf_get_task_stack() is to call
>>>> it from bpf_iter__task and dump all /proc/<pid>/stack to a seq_file.
>>>>
>>>> bpf_get_task_stack() uses stack_trace_save_tsk() instead of
>>>> get_perf_callchain() for kernel stack. The benefit of this choice is that
>>>> stack_trace_save_tsk() doesn't require changes in arch/. The downside of
>>>> using stack_trace_save_tsk() is that stack_trace_save_tsk() dumps the
>>>> stack trace to unsigned long array. For 32-bit systems, we need to
>>>> translate it to u64 array.
>>>>
>>>> Signed-off-by: Song Liu <songliubraving@fb.com>
>>>> ---
>>>
>>> Looks great, I just think that there are cases where user doesn't
>>> necessarily has valid task_struct pointer, just pid, so would be nice
>>> to not artificially restrict such cases by having extra helper.
>>>
>>> Acked-by: Andrii Nakryiko <andriin@fb.com>
>>
>> Thanks!
>>
>>>
>>>> include/linux/bpf.h | 1 +
>>>> include/uapi/linux/bpf.h | 35 ++++++++++++++-
>>>> kernel/bpf/stackmap.c | 79 ++++++++++++++++++++++++++++++++--
>>>> kernel/trace/bpf_trace.c | 2 +
>>>> scripts/bpf_helpers_doc.py | 2 +
>>>> tools/include/uapi/linux/bpf.h | 35 ++++++++++++++-
>>>> 6 files changed, 149 insertions(+), 5 deletions(-)
>>>>
>>>
>>> [...]
>>>
>>>> + /* stack_trace_save_tsk() works on unsigned long array, while
>>>> + * perf_callchain_entry uses u64 array. For 32-bit systems, it is
>>>> + * necessary to fix this mismatch.
>>>> + */
>>>> + if (__BITS_PER_LONG != 64) {
>>>> + unsigned long *from = (unsigned long *) entry->ip;
>>>> + u64 *to = entry->ip;
>>>> + int i;
>>>> +
>>>> + /* copy data from the end to avoid using extra buffer */
>>>> + for (i = entry->nr - 1; i >= (int)init_nr; i--)
>>>> + to[i] = (u64)(from[i]);
>>>
>>> doing this forward would be just fine as well, no? First iteration
>>> will cast and overwrite low 32-bits, all the subsequent iterations
>>> won't even overlap.
>>
>> I think first iteration will write zeros to higher 32 bits, no?
>
> Oh, wait, I completely misread what this is doing. It up-converts from
> 32-bit to 64-bit, sorry. Yeah, ignore me on this :)
>
> But then I have another question. How do you know that entry->ip has
> enough space to keep the same number of 2x bigger entries?
The buffer is sized for sysctl_perf_event_max_stack u64 numbers.
stack_trace_save_tsk() will put at most stack_trace_save_tsk unsigned
long in it (init_nr == 0). So the buffer is big enough.
Thanks,
Song
next prev parent reply other threads:[~2020-06-26 23:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 0:13 [PATCH v2 bpf-next 0/4] bpf: introduce bpf_get_task_stack() Song Liu
2020-06-26 0:13 ` [PATCH v2 bpf-next 1/4] perf: export get/put_chain_entry() Song Liu
2020-06-26 11:00 ` Peter Zijlstra
2020-06-26 20:06 ` Andrii Nakryiko
2020-06-26 21:38 ` Song Liu
2020-06-26 21:29 ` Song Liu
2020-06-26 0:13 ` [PATCH v2 bpf-next 2/4] bpf: introduce helper bpf_get_task_stak() Song Liu
2020-06-26 15:40 ` Yonghong Song
2020-06-26 22:37 ` Song Liu
2020-06-26 20:17 ` Andrii Nakryiko
2020-06-26 20:22 ` Andrii Nakryiko
2020-06-26 22:45 ` Song Liu
2020-06-26 22:51 ` Andrii Nakryiko
2020-06-26 23:47 ` Song Liu [this message]
2020-06-27 0:06 ` Andrii Nakryiko
2020-06-26 0:13 ` [PATCH v2 bpf-next 3/4] bpf: allow %pB in bpf_seq_printf() and bpf_trace_printk() Song Liu
2020-06-26 15:44 ` [Potential Spoof] " Yonghong Song
2020-06-26 0:13 ` [PATCH v2 bpf-next 4/4] selftests/bpf: add bpf_iter test with bpf_get_task_stack() Song Liu
2020-06-26 15:52 ` Yonghong Song
2020-06-26 20:21 ` Andrii Nakryiko
2020-06-26 23:05 ` Song Liu
2020-06-26 23:11 ` Andrii Nakryiko
2020-06-26 23:40 ` Song Liu
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=AD7AE0B3-94F9-4430-990C-85B9CF431EC7@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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).