Changes in Makefile

634f1a71 - vsock: support sockmap

Mon, 27 Mar 2023 19:11:51 +0000

vsock: support sockmapThis patch adds sockmap support for vsock sockets. It is intended to beusable by all transports, but only the virtio and loopback transportsare implemented.SOCK_STREAM, SOCK_DGRAM, and SOCK_SEQPACKET are all supported.Signed-off-by: Bobby Eshleman Acked-by: Michael S. Tsirkin Reviewed-by: Stefano Garzarella Signed-off-by: David S. Miller List of files: /linux-6.15/net/vmw_vsock/Makefile

077263fb - vsock: add vsock_loopback transport

Tue, 10 Dec 2019 10:43:05 +0000

vsock: add vsock_loopback transportThis patch adds a new vsock_loopback transport to handle localcommunication.This transport is based on the loopback implementation ofvirtio_transport, so it uses the virtio_transport_common APIsto interface with the vsock core.Signed-off-by: Stefano Garzarella Signed-off-by: David S. Miller List of files: /linux-6.15/net/vmw_vsock/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/net/vmw_vsock/Makefile

413a4317 - VSOCK: add sock_diag interface

Thu, 05 Oct 2017 20:46:53 +0000

VSOCK: add sock_diag interfaceThis patch adds the sock_diag interface for querying sockets fromuserspace. Tools like ss(8) and netstat(8) can use this interface tolist open sockets.The userspace ABI is defined in and includesnetlink request and response structs. The request can query socketsbased on their sk_state (e.g. listening sockets only) and the responsecontains socket information fields including the local/remote addresses,inode number, etc.This patch does not dump VMCI pending sockets because I have only testedthe virtio transport, which does not use pending sockets. Support canbe added later by extending vsock_diag_dump() if needed by VMCI users.Signed-off-by: Stefan Hajnoczi Signed-off-by: David S. Miller List of files: /linux-6.15/net/vmw_vsock/Makefile

ae0078fc - hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)

Sat, 26 Aug 2017 04:52:43 +0000

hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)Hyper-V Sockets (hv_sock) supplies a byte-stream based communicationmechanism between the host and the guest. It uses VMBus ringbuffer as thetransportation layer.With hv_sock, applications between the host (Windows 10, Windows Server2016 or newer) and the guest can talk with each other using the traditionalsocket APIs.More info about Hyper-V Sockets is available here:"Make your own integration services":https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-serviceThe patch implements the necessary support in Linux guest by introducing a newvsock transport for AF_VSOCK.Signed-off-by: Dexuan Cui Cc: K. Y. Srinivasan Cc: Haiyang Zhang Cc: Stephen Hemminger Cc: Andy King Cc: Dmitry Torokhov Cc: George Zhang Cc: Jorgen Hansen Cc: Reilly Grant Cc: Asias He Cc: Stefan Hajnoczi Cc: Vitaly Kuznetsov Cc: Cathy Avery Cc: Rolf Neugebauer Cc: Marcelo Cerri Signed-off-by: David S. Miller List of files: /linux-6.15/net/vmw_vsock/Makefile

531b3748 - VSOCK: Add vsockmon tap functions

Fri, 21 Apr 2017 09:10:44 +0000

VSOCK: Add vsockmon tap functionsAdd tap functions that can be used by the vsock transports todeliver packets to vsockmon virtual network devices.Signed-off-by: Gerard Garcia Signed-off-by: Stefan Hajnoczi Reviewed-by: Jorgen Hansen Signed-off-by: David S. Miller List of files: /linux-6.15/net/vmw_vsock/Makefile

304ba62f - VSOCK: Add Makefile and Kconfig

Thu, 28 Jul 2016 14:36:35 +0000

VSOCK: Add Makefile and KconfigEnable virtio-vsock and vhost-vsock.Signed-off-by: Asias He Signed-off-by: Stefan Hajnoczi Signed-off-by: Michael S. Tsirkin List of files: /linux-6.15/net/vmw_vsock/Makefile

8ac2837c - Revert "Merge branch 'vsock-virtio'"

Wed, 09 Dec 2015 02:51:12 +0000

Revert "Merge branch 'vsock-virtio'"This reverts commit 0d76d6e8b2507983a2cae4c09880798079007421 and mergecommit c402293bd76fbc93e52ef8c0947ab81eea3ae019, reversing changes madeto c89359a42e2a49656451569c382eed63e781153c.The virtio-vsock device specification is not finalized yet. MichaelTsirkin voiced concerned about merging this code when the hardwareinterface (and possibly the userspace interface) could still change.Signed-off-by: Stefan Hajnoczi Signed-off-by: David S. Miller List of files: /linux-6.15/net/vmw_vsock/Makefile

8a2a2029 - VSOCK: Add Makefile and Kconfig

Wed, 02 Dec 2015 06:44:03 +0000

VSOCK: Add Makefile and KconfigEnable virtio-vsock and vhost-vsock.Signed-off-by: Asias He Signed-off-by: Stefan Hajnoczi Signed-off-by: David S. Miller List of files: /linux-6.15/net/vmw_vsock/Makefile

d021c344 - VSOCK: Introduce VM Sockets

Wed, 06 Feb 2013 14:23:56 +0000

VSOCK: Introduce VM SocketsVM Sockets allows communication between virtual machines and the hypervisor.User level applications both in a virtual machine and on the host can use theVM Sockets API, which facilitates fast and efficient communication betweenguest virtual machines and their host. A socket address family, designed to becompatible with UDP and TCP at the interface level, is provided.Today, VM Sockets is used by various VMware Tools components inside the guestfor zero-config, network-less access to VMware host services. In addition tothis, VMware's users are using VM Sockets for various applications, wherenetwork access of the virtual machine is restricted or non-existent. Examplesof this are VMs communicating with device proxies for proprietary hardwarerunning as host applications and automated testing of applications runningwithin virtual machines.The VMware VM Sockets are similar to other socket types, like Berkeley UNIXsocket interface. The VM Sockets module supports both connection-orientedstream sockets like TCP, and connectionless datagram sockets like UDP. The VMSockets protocol family is defined as "AF_VSOCK" and the socket operationssplit for SOCK_DGRAM and SOCK_STREAM.For additional information about the use of VM Sockets, please refer to theVM Sockets Programming Guide available at:https://www.vmware.com/support/developer/vmci-sdk/Signed-off-by: George Zhang Signed-off-by: Dmitry Torokhov Signed-off-by: Andy king Signed-off-by: David S. Miller List of files: /linux-6.15/net/vmw_vsock/Makefile