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  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:   Tue, 15 Dec 2020 03:40:08 +0000
To:, Andra-Irina <>
Subject: Re: [PATCH net-next v4 0/5] vsock: Add flags field in the vsock address


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

On Mon, 14 Dec 2020 18:11:17 +0200 you wrote:
> vsock enables communication between virtual machines and the host they are
> running on. Nested VMs can be setup to use vsock channels, as the multi
> transport support has been available in the mainline since the v5.5 Linux kernel
> has been released.
> Implicitly, if no host->guest vsock transport is loaded, all the vsock packets
> are forwarded to the host. This behavior can be used to setup communication
> channels between sibling VMs that are running on the same host. One example can
> be the vsock channels that can be established within AWS Nitro Enclaves
> (see Documentation/virt/ne_overview.rst).
> [...]

Here is the summary with links:
  - [net-next,v4,1/5] vm_sockets: Add flags field in the vsock address data structure
  - [net-next,v4,2/5] vm_sockets: Add VMADDR_FLAG_TO_HOST vsock flag
  - [net-next,v4,3/5] vsock_addr: Check for supported flag values
  - [net-next,v4,4/5] af_vsock: Set VMADDR_FLAG_TO_HOST flag on the receive path
  - [net-next,v4,5/5] af_vsock: Assign the vsock transport considering the vsock address flags

You are awesome, thank you!
Deet-doot-dot, I am a bot.

Powered by blists - more mailing lists