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]
Date:   Thu, 08 Dec 2022 18:10:15 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Björn Töpel <bjorn@...nel.org>@ci.codeaurora.org
Cc:     ast@...nel.org, daniel@...earbox.net, john.fastabend@...il.com,
        bpf@...r.kernel.org, netdev@...r.kernel.org, bjorn@...osinc.com,
        iii@...ux.ibm.com, jackmanb@...gle.com, yhs@...a.com,
        yangjihong1@...wei.com
Subject: Re: [PATCH bpf v2] bpf: Do not zero-extend kfunc return values

Hello:

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

On Wed,  7 Dec 2022 11:35:40 +0100 you wrote:
> From: Björn Töpel <bjorn@...osinc.com>
> 
> In BPF all global functions, and BPF helpers return a 64-bit
> value. For kfunc calls, this is not the case, and they can return
> e.g. 32-bit values.
> 
> The return register R0 for kfuncs calls can therefore be marked as
> subreg_def != DEF_NOT_SUBREG. In general, if a register is marked with
> subreg_def != DEF_NOT_SUBREG, some archs (where bpf_jit_needs_zext()
> returns true) require the verifier to insert explicit zero-extension
> instructions.
> 
> [...]

Here is the summary with links:
  - [bpf,v2] bpf: Do not zero-extend kfunc return values
    https://git.kernel.org/bpf/bpf-next/c/d35af0a7feb0

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