From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BF406C433FE for ; Fri, 4 Nov 2022 05:00:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229507AbiKDFAU (ORCPT ); Fri, 4 Nov 2022 01:00:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36660 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229539AbiKDFAT (ORCPT ); Fri, 4 Nov 2022 01:00:19 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0E66B1C924 for ; Thu, 3 Nov 2022 22:00:19 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 954036209A for ; Fri, 4 Nov 2022 05:00:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id A91A6C43155; Fri, 4 Nov 2022 05:00:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1667538017; bh=dgnTW3gLRv1yQcPfocY9KSqqU29bKGmhSN1OU80cCxM=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=dEQetfemwSpRe0rOqdjnJwh8VwE8iqk2mRuQns/q90rAi6aIcPK9APIIQReVKpgfS HcMFKVE55ivAIXEwStxpqRlf4oZ7h2CNMIV2+dVPT8zO3vpZCiqZHU3aedk9FMptm0 dvcAGY4ay/KwHk5nrdPwrWe084TQMRVXKj7xN1KUFozSfB4GRWxIPuoqfSvlfAa2LB 1kJQiVFCF2Ni/Y3FRD3HqHJeMVjB9Eqtr3fYtZfXaXRiEq2qw5uS5i1qWGFOls5UKn AM6X1dYhS41JiCJ5pteXRgx0u8LA8FZ2ZkSKuYgMxu1OjtJsMjeWk2fMgFMvMH8RXR eKlJsDvhghmlQ== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 7DB9CE270EA; Fri, 4 Nov 2022 05:00:17 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH bpf-next v4 00/24] Local kptrs, BPF linked lists From: patchwork-bot+netdevbpf@kernel.org Message-Id: <166753801750.27738.4286004544054284287.git-patchwork-notify@kernel.org> Date: Fri, 04 Nov 2022 05:00:17 +0000 References: <20221103191013.1236066-1-memxor@gmail.com> In-Reply-To: <20221103191013.1236066-1-memxor@gmail.com> To: Kumar Kartikeya Dwivedi Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org, davemarchevsky@meta.com, delyank@meta.com Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Hello: This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov : On Fri, 4 Nov 2022 00:39:49 +0530 you wrote: > This series introduces user defined BPF objects, by introducing the idea > of local kptrs. These are kptrs (strongly typed pointers) that refer to > objects of a user defined type, hence called "local" kptrs. This allows > BPF programs to allocate their own objects, build their own object > hierarchies, and use the basic building blocks provided by BPF runtime > to build their own data structures flexibly. > > [...] Here is the summary with links: - [bpf-next,v4,01/24] bpf: Document UAPI details for special BPF types https://git.kernel.org/bpf/bpf-next/c/9805af8d8a5b - [bpf-next,v4,02/24] bpf: Allow specifying volatile type modifier for kptrs https://git.kernel.org/bpf/bpf-next/c/23da464dd6b8 - [bpf-next,v4,03/24] bpf: Clobber stack slot when writing over spilled PTR_TO_BTF_ID https://git.kernel.org/bpf/bpf-next/c/261f4664caff - [bpf-next,v4,04/24] bpf: Fix slot type check in check_stack_write_var_off https://git.kernel.org/bpf/bpf-next/c/f5e477a861e4 - [bpf-next,v4,05/24] bpf: Drop reg_type_may_be_refcounted_or_null https://git.kernel.org/bpf/bpf-next/c/a28ace782e68 - [bpf-next,v4,06/24] bpf: Refactor kptr_off_tab into btf_record https://git.kernel.org/bpf/bpf-next/c/aa3496accc41 - [bpf-next,v4,07/24] bpf: Consolidate spin_lock, timer management into btf_record (no matching commit) - [bpf-next,v4,08/24] bpf: Refactor map->off_arr handling (no matching commit) - [bpf-next,v4,09/24] bpf: Support bpf_list_head in map values (no matching commit) - [bpf-next,v4,10/24] bpf: Introduce local kptrs (no matching commit) - [bpf-next,v4,11/24] bpf: Recognize bpf_{spin_lock,list_head,list_node} in local kptrs (no matching commit) - [bpf-next,v4,12/24] bpf: Verify ownership relationships for user BTF types (no matching commit) - [bpf-next,v4,13/24] bpf: Support locking bpf_spin_lock in local kptr (no matching commit) - [bpf-next,v4,14/24] bpf: Allow locking bpf_spin_lock global variables (no matching commit) - [bpf-next,v4,15/24] bpf: Rewrite kfunc argument handling (no matching commit) - [bpf-next,v4,16/24] bpf: Drop kfunc bits from btf_check_func_arg_match (no matching commit) - [bpf-next,v4,17/24] bpf: Support constant scalar arguments for kfuncs (no matching commit) - [bpf-next,v4,18/24] bpf: Teach verifier about non-size constant arguments (no matching commit) - [bpf-next,v4,19/24] bpf: Introduce bpf_obj_new (no matching commit) - [bpf-next,v4,20/24] bpf: Introduce bpf_obj_drop (no matching commit) - [bpf-next,v4,21/24] bpf: Permit NULL checking pointer with non-zero fixed offset (no matching commit) - [bpf-next,v4,22/24] bpf: Introduce single ownership BPF linked list API (no matching commit) - [bpf-next,v4,23/24] selftests/bpf: Add __contains macro to bpf_experimental.h (no matching commit) - [bpf-next,v4,24/24] selftests/bpf: Add BPF linked list API tests (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html