netdev - Re: [PATCH bpf-next] bpf, sockmap: fix return codes from tcp_bpf_recvmsg

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: <164141220983.28548.2255582640543203112.git-patchwork-notify@kernel.org>
Date:   Wed, 05 Jan 2022 19:50:09 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     John Fastabend <john.fastabend@...il.com>
Cc:     ast@...nel.org, daniel@...earbox.net, netdev@...r.kernel.org,
        bpf@...r.kernel.org, joamaki@...il.com
Subject: Re: [PATCH bpf-next] bpf,
 sockmap: fix return codes from tcp_bpf_recvmsg_parser()

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.net>:

On Tue,  4 Jan 2022 12:59:18 -0800 you wrote:
> Applications can be confused slightly because we do not always return the
> same error code as expected, e.g. what the TCP stack normally returns. For
> example on a sock err sk->sk_err instead of returning the sock_error we
> return EAGAIN. This usually means the application will 'try again'
> instead of aborting immediately. Another example, when a shutdown event
> is received we should immediately abort instead of waiting for data when
> the user provides a timeout.
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf, sockmap: fix return codes from tcp_bpf_recvmsg_parser()
    https://git.kernel.org/bpf/bpf-next/c/5b2c5540b811

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