netdev - Re: [PATCH net-next] rxrpc: use udp tunnel APIs instead of open code in rxrpc_open

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 08 Feb 2021 23:20:07 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Xin Long <lucien.xin@...il.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        dhowells@...hat.com
Subject: Re: [PATCH net-next] rxrpc: use udp tunnel APIs instead of open code in
 rxrpc_open_socket

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Sun,  7 Feb 2021 16:23:14 +0800 you wrote:
> In rxrpc_open_socket(), now it's using sock_create_kern() and
> kernel_bind() to create a udp tunnel socket, and other kernel
> APIs to set up it. These code can be replaced with udp tunnel
> APIs udp_sock_create() and setup_udp_tunnel_sock(), and it'll
> simplify rxrpc_open_socket().
> 
> Note that with this patch, the udp tunnel socket will always
> bind to a random port if transport is not provided by users,
> which is suggested by David Howells, thanks!
> 
> [...]

Here is the summary with links:
  - [net-next] rxrpc: use udp tunnel APIs instead of open code in rxrpc_open_socket
    https://git.kernel.org/netdev/net-next/c/1a9b86c9fd95

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