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] [day] [month] [year] [list]
Message-Id: <164366242265.17453.14979978699179482148.git-patchwork-notify@kernel.org>
Date:   Mon, 31 Jan 2022 20:53:42 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jakub Sitnicki <jakub@...udflare.com>
Cc:     bpf@...r.kernel.org, netdev@...r.kernel.org, ast@...nel.org,
        daniel@...earbox.net, andrii@...nel.org, imagedong@...cent.com,
        kafai@...com
Subject: Re: [PATCH bpf-next v2 0/2] Split bpf_sock dst_port field

Hello:

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

On Sun, 30 Jan 2022 12:55:16 +0100 you wrote:
> This is a follow-up to discussion around the idea of making dst_port in struct
> bpf_sock a 16-bit field that happened in [1].
> 
> v2:
> - use an anonymous field for zero padding (Alexei)
> 
> v1:
> - keep dst_field offset unchanged to prevent existing BPF program breakage
>   (Martin)
> - allow 8-bit loads from dst_port[0] and [1]
> - add test coverage for the verifier and the context access converter
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: Make dst_port field in struct bpf_sock 16-bit wide
    https://git.kernel.org/bpf/bpf-next/c/4421a582718a
  - [bpf-next,v2,2/2] selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
    https://git.kernel.org/bpf/bpf-next/c/8f50f16ff39d

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