From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 192B4C34024 for ; Mon, 17 Feb 2020 17:31:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E540E20718 for ; Mon, 17 Feb 2020 17:31:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="PSFsu9Bq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728575AbgBQRb3 (ORCPT ); Mon, 17 Feb 2020 12:31:29 -0500 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:29331 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728054AbgBQRb3 (ORCPT ); Mon, 17 Feb 2020 12:31:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581960687; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=RDNr8uSJFx59Jhf7UFuMY4MdIqV6VZNKPmJEIQeiPFg=; b=PSFsu9BqksDSDC5Xsvpv34YO/dsbThoB1edttJVfTIBLFyqR98G0prdEtrW+6G1zAlH+6a bZSjGPiY97UCawkgNDVUm5fZuOTXNOaamvREoyIYsJOKsvsg8IIER1KP+W1gAxl06NyxDU HtxnIy4PR1MRCV3Tx0oh6CHqZWgD5Ms= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-395-yGY72TkzOg6wpjCrhVFzLA-1; Mon, 17 Feb 2020 12:31:25 -0500 X-MC-Unique: yGY72TkzOg6wpjCrhVFzLA-1 Received: by mail-wm1-f72.google.com with SMTP id 7so51568wmf.9 for ; Mon, 17 Feb 2020 09:31:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=RDNr8uSJFx59Jhf7UFuMY4MdIqV6VZNKPmJEIQeiPFg=; b=KBRnKdnwZnXBXx/s87HBO/6Co5bk0vA9kfNWzuaNdeuiJuS1TgOWU4rsSl31HiOguH lGOgFzguONTE9JTPvLxaqHNywCTmXl8LE892z0alqmHw0Vj15vNf/V1/3ZMUhR7puj+9 QeSGD8MF51iyNZ0FuP/8wcIavW6gBQP7Bygb0aR1ZZqgPdMGgzLI7V/1q/H53/zM71+Z nYamJYaUbvvtBd3/cSrfllDapDnGOoPxQI6+SuAe1g4kP758nqm8M8A+24/pFVFyyeTB Q4cJ8lO+XmHEFnlUgZzLVr8ct5jdqKyxlo8SfddW6aJLkJSVKGaqjrgVb/Tiaui9yeUT 3Jjg== X-Gm-Message-State: APjAAAVYENAHvfST1/csQI0uPRYeeTzd+/SYpr3vtIN92wIbERkXZech l0C7M6qJ5ORBen6BWR+KSeayJ1HZ1un9lS+ZmGE0tEmZB2Q3jS04SVU7y1mBwY/A52xYWrLo3hC s8fpqTYI8ISMtUMDR/hij X-Received: by 2002:a1c:a9c4:: with SMTP id s187mr83154wme.97.1581960684884; Mon, 17 Feb 2020 09:31:24 -0800 (PST) X-Google-Smtp-Source: APXvYqydEgIaLAMeg8L3wmkxuEFr+1Usg0RMHSX1PoJkBi8Zw0lHfES2eqo1OOcB+81A9ChrE+B7Jw== X-Received: by 2002:a1c:a9c4:: with SMTP id s187mr83076wme.97.1581960683665; Mon, 17 Feb 2020 09:31:23 -0800 (PST) Received: from steredhat.redhat.com (host209-4-dynamic.27-79-r.retail.telecomitalia.it. [79.27.4.209]) by smtp.gmail.com with ESMTPSA id b13sm1924870wrq.48.2020.02.17.09.31.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Feb 2020 09:31:23 -0800 (PST) From: Stefano Garzarella To: mtk.manpages@gmail.com Cc: linux-man@vger.kernel.org, Dexuan Cui , Stefan Hajnoczi , Jorgen Hansen , netdev@vger.kernel.org Subject: [PATCH v3] vsock.7: add VMADDR_CID_LOCAL description Date: Mon, 17 Feb 2020 18:31:21 +0100 Message-Id: <20200217173121.159132-1-sgarzare@redhat.com> X-Mailer: git-send-email 2.24.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-man-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org Linux 5.6 added the new well-known VMADDR_CID_LOCAL for local communication. This patch explains how to use it and remove the legacy VMADDR_CID_RESERVED no longer available. Reviewed-by: Jorgen Hansen Signed-off-by: Stefano Garzarella --- v3: * rephrased "Previous versions" part [Jorgen] v2: * rephrased "Local communication" description [Stefan] * added a mention of previous versions that supported loopback only in the guest [Stefan] --- man7/vsock.7 | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/man7/vsock.7 b/man7/vsock.7 index c5ffcf07d..219e3505f 100644 --- a/man7/vsock.7 +++ b/man7/vsock.7 @@ -127,8 +127,8 @@ There are several special addresses: means any address for binding; .B VMADDR_CID_HYPERVISOR (0) is reserved for services built into the hypervisor; -.B VMADDR_CID_RESERVED -(1) must not be used; +.B VMADDR_CID_LOCAL +(1) is the well-known address for local communication (loopback); .B VMADDR_CID_HOST (2) is the well-known address of the host. @@ -164,6 +164,16 @@ Consider using .B VMADDR_CID_ANY when binding instead of getting the local CID with .BR IOCTL_VM_SOCKETS_GET_LOCAL_CID . +.SS Local communication +The +.B VMADDR_CID_LOCAL +(1) directs packets to the same host that generated them. This is useful +for testing applications on a single host and for debugging. +.PP +The local CID obtained with +.BR IOCTL_VM_SOCKETS_GET_LOCAL_CID +can be used for the same purpose, but it is preferable to use +.B VMADDR_CID_LOCAL . .SH ERRORS .TP .B EACCES @@ -222,6 +232,11 @@ are valid. Support for VMware (VMCI) has been available since Linux 3.9. KVM (virtio) is supported since Linux 4.8. Hyper-V is supported since Linux 4.14. +.PP +VMADDR_CID_LOCAL is supported since Linux 5.6. +Local communication in the guest and on the host is available since Linux 5.6. +Previous versions only supported local communication within a guest +(not on the host), and only with some transports (VMCI and virtio). .SH SEE ALSO .BR bind (2), .BR connect (2), -- 2.24.1