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=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 52030C2D0DB for ; Mon, 20 Jan 2020 12:03:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 22FC6208E4 for ; Mon, 20 Jan 2020 12:03:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="WJS8HB1M" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726867AbgATMDa (ORCPT ); Mon, 20 Jan 2020 07:03:30 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:57538 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726798AbgATMDa (ORCPT ); Mon, 20 Jan 2020 07:03:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579521809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=i0FYwpPvJVwXX6WibGdKe3t8GmO0Q/BB/ry3XOYj5v4=; b=WJS8HB1MwKu4ra39GjmNVVbOKhp+CQ93svNMvRi49/CEbf5IUm272ey48bxukyq3Uhr0Xj n/IPNUZJpTz1VlbdP6ih2CVzgNoOwnt8/zovVjtWWTfmrCzlCZZBioH3NGrW5RZ/ePK+GX hyb/mTh5QhOhAICGAMD0hLmfaxY4/co= Received: from mail-qt1-f197.google.com (mail-qt1-f197.google.com [209.85.160.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-377-wh_GBNC2P0SGpx7lEXTgow-1; Mon, 20 Jan 2020 07:03:28 -0500 X-MC-Unique: wh_GBNC2P0SGpx7lEXTgow-1 Received: by mail-qt1-f197.google.com with SMTP id d9so21039923qtq.13 for ; Mon, 20 Jan 2020 04:03:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=i0FYwpPvJVwXX6WibGdKe3t8GmO0Q/BB/ry3XOYj5v4=; b=mXH4Xds53Thrh4UvrIdDoVHJQhdRduPcagNj+BCiJrOCbyePPXfKFobn0BLsZ3Ja/Z JpZMtN4ByFylpJ4ur5iwXjAfMzkX5PnoVfFEBHTAir6fhNJcZO+bIEBg8ybHwwpEmDXd yMFaMGUU2FN5uSVu/AYzaB6hifRXSuD1xu+/Su3reToX+cLgr7LhGbo7+Dj/mSuIHno5 koEzK4ObaWgXPo67RqlUljdjSaGfvE91VsrBvO4N+ruBARFLZNORLNTH3SGEFYUU7srt Qhh3I2/pp0CjpRR4FKiz1WEA64m891wvnUPPBe73fI1n3VO+aaFrtT+Xw1P7GStPVjMZ guGA== X-Gm-Message-State: APjAAAVT2IUHTFibReXFLaFZReJgztge3xgY8PS47jGWapWCghyYZ2HP BopcDqq8VkAJJeDl8eQK+muIR9BzNxT+/wm5Zc04gL4J2gpPJJXssHkW1m/f6IeFnuj1LsxZljZ VDH6vBHO2+BIw X-Received: by 2002:ac8:2c7d:: with SMTP id e58mr20372313qta.196.1579521807754; Mon, 20 Jan 2020 04:03:27 -0800 (PST) X-Google-Smtp-Source: APXvYqwBOvpzVbluzRk2PBevjR+yTn5PHKpCN1mkjbfx/S5QQmnZyFB/1WiP+Ct1GD9bo9yvXG9y7A== X-Received: by 2002:ac8:2c7d:: with SMTP id e58mr20372288qta.196.1579521807486; Mon, 20 Jan 2020 04:03:27 -0800 (PST) Received: from redhat.com (bzq-79-179-85-180.red.bezeqint.net. [79.179.85.180]) by smtp.gmail.com with ESMTPSA id h8sm17044762qtm.51.2020.01.20.04.03.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Jan 2020 04:03:26 -0800 (PST) Date: Mon, 20 Jan 2020 07:03:20 -0500 From: "Michael S. Tsirkin" To: Stefano Garzarella Cc: David Miller , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, jhansen@vmware.com, jasowang@redhat.com, kvm@vger.kernel.org, stefanha@redhat.com, virtualization@lists.linux-foundation.org, linux-hyperv@vger.kernel.org, decui@microsoft.com Subject: Re: [PATCH net-next 1/3] vsock: add network namespace support Message-ID: <20200120060601-mutt-send-email-mst@kernel.org> References: <20200116172428.311437-1-sgarzare@redhat.com> <20200116172428.311437-2-sgarzare@redhat.com> <20200120.100610.546818167633238909.davem@davemloft.net> <20200120101735.uyh4o64gb4njakw5@steredhat> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200120101735.uyh4o64gb4njakw5@steredhat> Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Mon, Jan 20, 2020 at 11:17:35AM +0100, Stefano Garzarella wrote: > On Mon, Jan 20, 2020 at 10:06:10AM +0100, David Miller wrote: > > From: Stefano Garzarella > > Date: Thu, 16 Jan 2020 18:24:26 +0100 > > > > > This patch adds 'netns' module param to enable this new feature > > > (disabled by default), because it changes vsock's behavior with > > > network namespaces and could break existing applications. > > > > Sorry, no. > > > > I wonder if you can even design a legitimate, reasonable, use case > > where these netns changes could break things. > > I forgot to mention the use case. > I tried the RFC with Kata containers and we found that Kata shim-v1 > doesn't work (Kata shim-v2 works as is) because there are the following > processes involved: > - kata-runtime (runs in the init_netns) opens /dev/vhost-vsock and > passes it to qemu > - kata-shim (runs in a container) wants to talk with the guest but the > vsock device is assigned to the init_netns and kata-shim runs in a > different netns, so the communication is not allowed > But, as you said, this could be a wrong design, indeed they already > found a fix, but I was not sure if others could have the same issue. > > In this case, do you think it is acceptable to make this change in > the vsock's behavior with netns and ask the user to change the design? David's question is what would be a usecase that's broken (as opposed to fixed) by enabling this by default. If it does exist, you need a way for userspace to opt-in, module parameter isn't that. > > > > > I am totally against adding a module parameter for this, it's > > incredibly confusing for users and will create a test scenerio > > that is strongly less likely to be covered. > > > > Got it, I'll remove the module parameter! > > Thanks, > Stefano