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] [thread-next>] [day] [month] [year] [list]
Message-Id: <166896541652.21684.9432538725103105426.git-patchwork-notify@kernel.org>
Date:   Sun, 20 Nov 2022 17:30:16 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     David Vernet <void@...ifault.com>
Cc:     ast@...nel.org, andrii@...nel.org, daniel@...earbox.net,
        martin.lau@...ux.dev, yhs@...com, song@...nel.org, sdf@...gle.com,
        john.fastabend@...il.com, haoluo@...gle.com, jolsa@...nel.org,
        kpsingh@...nel.org, memxor@...il.com, tj@...nel.org,
        bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
        kernel-team@...com
Subject: Re: [PATCH bpf-next v9 0/4] Support storing struct task_struct objects as
 kptrs

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:

On Sat, 19 Nov 2022 23:10:00 -0600 you wrote:
> Now that BPF supports adding new kernel functions with kfuncs, and
> storing kernel objects in maps with kptrs, we can add a set of kfuncs
> which allow struct task_struct objects to be stored in maps as
> referenced kptrs.
> 
> The possible use cases for doing this are plentiful.  During tracing,
> for example, it would be useful to be able to collect some tasks that
> performed a certain operation, and then periodically summarize who they
> are, which cgroup they're in, how much CPU time they've utilized, etc.
> Doing this now would require storing the tasks' pids along with some
> relevant data to be exported to user space, and later associating the
> pids to tasks in other event handlers where the data is recorded.
> Another useful by-product of this is that it allows a program to pin a
> task in a BPF program, and by proxy therefore also e.g. pin its task
> local storage.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v9,1/4] bpf: Allow multiple modifiers in reg_type_str() prefix
    https://git.kernel.org/bpf/bpf-next/c/ef66c5475d7f
  - [bpf-next,v9,2/4] bpf: Allow trusted pointers to be passed to KF_TRUSTED_ARGS kfuncs
    https://git.kernel.org/bpf/bpf-next/c/3f00c5239344
  - [bpf-next,v9,3/4] bpf: Add kfuncs for storing struct task_struct * as a kptr
    https://git.kernel.org/bpf/bpf-next/c/90660309b0c7
  - [bpf-next,v9,4/4] bpf/selftests: Add selftests for new task kfuncs
    https://git.kernel.org/bpf/bpf-next/c/fe147956fca4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ