Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH bpf-next v2 0/9] Enable cpumasks to be used as kptrs
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167462161665.8470.7244847116038822799.git-patchwork-notify@kernel.org>
Date:   Wed, 25 Jan 2023 04:40:16 +0000
References: <20230120192523.3650503-1-void@manifault.com>
In-Reply-To: <20230120192523.3650503-1-void@manifault.com>
To:     David Vernet <void@manifault.com>
Cc:     bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
        andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
        yhs@meta.com, john.fastabend@gmail.com, kpsingh@kernel.org,
        sdf@google.com, haoluo@google.com, jolsa@kernel.org,
        linux-kernel@vger.kernel.org, kernel-team@meta.com, tj@kernel.org,
        memxor@gmail.com
Precedence: bulk

Hello:

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

On Fri, 20 Jan 2023 13:25:14 -0600 you wrote:
> This is part 2 of https://lore.kernel.org/all/20230119235833.2948341-1-void@manifault.com/
> 
> Changelog:
> ----------
> v1 -> v2:
> - Put back 'static' keyword in bpf_find_btf_id()
>   (kernel test robot <lkp@intel.com>)
> - Surround cpumask kfuncs in __diag() blocks to avoid no-prototype build
>   warnings (kernel test robot <lkp@intel.com>)
> - Enable ___init suffixes to a type definition to signal that a type is
>   a nocast alias of another type. That is, that when passed to a kfunc
>   that expects one of the two types, the verifier will reject the other
>   even if they're equivalent according to the C standard (Kumar and
>   Alexei)
> - Reject NULL for all trusted args, not just PTR_TO_MEM (Kumar)
> - Reject both NULL and PTR_MAYBE_NULL for all trusted args (Kumar and
>   Alexei )
> - Improve examples given in cpumask documentation (Alexei)
> - Use __success macro for nested_trust test (Alexei)
> - Fix comment typo in struct bpf_cpumask comment header.
> - Fix another example in the bpf_cpumask doc examples.
> - Add documentation for ___init suffix change mentioned above.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/9] bpf: Enable annotating trusted nested pointers
    https://git.kernel.org/bpf/bpf-next/c/57539b1c0ac2
  - [bpf-next,v2,2/9] bpf: Allow trusted args to walk struct when checking BTF IDs
    https://git.kernel.org/bpf/bpf-next/c/b613d335a743
  - [bpf-next,v2,3/9] bpf: Disallow NULLable pointers for trusted kfuncs
    (no matching commit)
  - [bpf-next,v2,4/9] bpf: Enable cpumasks to be queried and used as kptrs
    (no matching commit)
  - [bpf-next,v2,5/9] selftests/bpf: Add nested trust selftests suite
    (no matching commit)
  - [bpf-next,v2,6/9] selftests/bpf: Add selftest suite for cpumask kfuncs
    (no matching commit)
  - [bpf-next,v2,7/9] bpf/docs: Document cpumask kfuncs in a new file
    (no matching commit)
  - [bpf-next,v2,8/9] bpf/docs: Document how nested trusted fields may be defined
    (no matching commit)
  - [bpf-next,v2,9/9] bpf/docs: Document the nocast aliasing behavior of ___init
    (no matching commit)

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