From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oa1-f50.google.com (mail-oa1-f50.google.com [209.85.160.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 58E3A23817F for ; Wed, 24 Dec 2025 02:17:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.160.50 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766542641; cv=none; b=UVed7QHX50LMBadGJelwpbGdFiRQIp9xPRMV6D70bgg0mqiQ9O7ye4TjrIvk1vamUprV/NCJQVrjLTQbFBzkkdQoVWLwnsZK4Sf9ZLkmk7SPW0Rx7vPq2kkiX4qaLOKRztqWf7oF0+4yG741baMssP56kWZYDs01sXZ1rUgjBmg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766542641; c=relaxed/simple; bh=fag3FxlJG3ZXO56Q4uis4IXo7o2vEhpJMwuQCgBCfc8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=kdhbYhsJ5nXdHEfV1R0jUaM9IKi79dCrl6dyRrSdrb/pQETL1XyPpGLsXjA044k7MVV+hYviogBSSkDk/upOAPpNpnKCKxhnY7E9AIXG5tasdGKm/avYflXrcJnrXgndE7YCZtSGK22KMzK+D+I5wS3A4bSdxd4aSQ73mkm+gZA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=Wg1qEyDG; arc=none smtp.client-ip=209.85.160.50 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Wg1qEyDG" Received: by mail-oa1-f50.google.com with SMTP id 586e51a60fabf-3f0ec55ce57so3800790fac.2 for ; Tue, 23 Dec 2025 18:17:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1766542638; x=1767147438; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=Mn5gdOJNVLCgqxTAZaOj5KghlS4vIZEHYcNf0bwJm28=; b=Wg1qEyDGQNZ5neOD25jMMskg3UzH+Yy+n2Pdd+XPu1E3+AouwmG3SW546ptlSelilz gy8olX+RDd3+LaF9qamqnxZ6yGNmkN2z0sJ0neyloYD83zo0JCIA+abJne77Zbn+OpUH Kd+p+zCzPz5jSnUmWJJKwSu6hEK5efU/OBzcqzg8ULR4yxPeBpN8No4L9epIqUEWy6rX xhkUHd4MIvHQV7n7pSK/SrYe06s27gKoMaAT4igkXXmt08EGJjzj6FS7H/WsU20DA/Rf eK626cTtv3TCckitW7LAlyETFkOygzOYi9QcQ7h0a4L03TR5DFVs6nihrksCuhjJVh57 LvDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1766542638; x=1767147438; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Mn5gdOJNVLCgqxTAZaOj5KghlS4vIZEHYcNf0bwJm28=; b=vr+Tqmasrk+ROXVj7RvBUDWm4R0T5R/+7JCPp25MuuGEWuKeHv0+difpOmVQmWYc3x EJz1XTQ9Njmu/LpErKvVBXPXtoTBKb+72qK816F3J3aKWZe9ogjJvadxfc8c18ABdnA8 0soX7vhvOYtX4+Wbxek3ssrz41DLKhVVINvHdOpRDQLA3lUkDPd/QetalX0tvSVoUHjh djsP4Dxt4mCaJKXCS3AJwxTCWGTR402QMR8KmobxPvb0lF73Uys1o5pfCuQ+rKLI0h2A Bf9tf7P14XViSU5VHz072p/hlOkoFq82hBnp2lsfUqA7HuYEB3ozmd0GPHSJmriILKMB Bp/w== X-Forwarded-Encrypted: i=1; AJvYcCW6jZ5ccnPJfmzFrFJFq7/7WhYnbUb4HdYTaz+7sxuJUDcpk1m3cOiDwoaFBLkD1SI+b+rpplXt2Qu3BvQ=@vger.kernel.org X-Gm-Message-State: AOJu0Yx2yAAnkM+BQl77Sb5cnLYeghNW9lh9bNTd98k5YBrzQKbht1oX nGgBRow1WeiVR95htMwGri1zx5zJ9oA+VhyW2wQmsCli8CjmZNzsuoL4UaG10Q== X-Gm-Gg: AY/fxX5rx+9L6CqPnR7NwFVivqsBoJPjnoOoONYI4qYeuH8VjcNH7F//d+arMePGdBo Cc1QC4FFoXYHGLkKXoy6q4c8hV9BjVw34wGd4093SRXH8T6bVHPvQLKdKR28f5EZsXmZWi3iJ7x 1nLcg3aFS/zXip/EDUOBKhVeOinzAv1MaAYE1PyKvYvSpamampixe6gbYOr77nK5c0PYWD/YdYD nLAtHkdIMF/5DHmFjNqgUss5B7UIM9dJ3lTa1vwCuUnsgtA0hNh+ZrlLy1khHZVwx37aBsVQjmG ljWxxOBfUv/6ApDa44NrApGn12YKwptXvlru2+Ul3rT1jc1INI9Eh3DkqxnmxQmFh16dP0wSxPD 11JuGn0Kr8wvO9klxbO8Cw3fzhqEGVR3pcA2s9ZKXH5ScG7IP43UEQAVbbjmxzEO91iPlNOCeDk BTlMCQWxTJY9Qpy06ioQ4GQfilfkYk3B09PunjoJ3WMZp5VyA= X-Google-Smtp-Source: AGHT+IGl4lY3C5uaIhAdAeU51l9QnKvRP/mJp5bbTNMXCgmCDrIGHmPARt/rlh3H/cQnB4TIEc9mUg== X-Received: by 2002:a05:690c:d96:b0:78f:aa6d:48cd with SMTP id 00721157ae682-78fb3d52b45mr134838347b3.0.1766536355576; Tue, 23 Dec 2025 16:32:35 -0800 (PST) Received: from devvm11784.nha0.facebook.com ([2a03:2880:25ff:5f::]) by smtp.gmail.com with ESMTPSA id 00721157ae682-78fb4378372sm59887097b3.12.2025.12.23.16.32.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Dec 2025 16:32:35 -0800 (PST) Date: Tue, 23 Dec 2025 16:32:30 -0800 From: Bobby Eshleman To: Stefano Garzarella Cc: Paolo Abeni , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Simon Horman , Stefan Hajnoczi , "Michael S. Tsirkin" , Jason Wang , Eugenio =?iso-8859-1?Q?P=E9rez?= , Xuan Zhuo , "K. Y. Srinivasan" , Haiyang Zhang , Wei Liu , Dexuan Cui , Bryan Tan , Vishnu Dasa , Broadcom internal kernel review list , Shuah Khan , linux-kernel@vger.kernel.org, virtualization@lists.linux.dev, netdev@vger.kernel.org, kvm@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-kselftest@vger.kernel.org, berrange@redhat.com, Sargun Dhillon , Bobby Eshleman Subject: Re: [PATCH net-next v12 04/12] vsock: add netns support to virtio transports Message-ID: References: <20251126-vsock-vmtest-v12-0-257ee21cd5de@meta.com> <20251126-vsock-vmtest-v12-4-257ee21cd5de@meta.com> <6cef5a68-375a-4bb6-84f8-fccc00cf7162@redhat.com> <06b7cfea-d366-44f7-943e-087ead2f25c2@redhat.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Mon, Dec 15, 2025 at 05:22:02PM -0800, Bobby Eshleman wrote: > On Mon, Dec 15, 2025 at 03:11:22PM +0100, Stefano Garzarella wrote: > > On Fri, Dec 12, 2025 at 07:26:15AM -0800, Bobby Eshleman wrote: > > > On Tue, Dec 02, 2025 at 02:01:04PM -0800, Bobby Eshleman wrote: > > > > On Tue, Dec 02, 2025 at 09:47:19PM +0100, Paolo Abeni wrote: > > > > > On 12/2/25 6:56 PM, Bobby Eshleman wrote: > > > > > > On Tue, Dec 02, 2025 at 11:18:14AM +0100, Paolo Abeni wrote: > > > > > >> On 11/27/25 8:47 AM, Bobby Eshleman wrote: > > > > > >>> @@ -674,6 +689,17 @@ static int vhost_vsock_dev_open(struct inode *inode, struct file *file) > > > > > >>> goto out; > > > > > >>> } > > > > > >>> > > > > > >>> + net = current->nsproxy->net_ns; > > > > > >>> + vsock->net = get_net_track(net, &vsock->ns_tracker, GFP_KERNEL); > > > > > >>> + > > > > > >>> + /* Store the mode of the namespace at the time of creation. If this > > > > > >>> + * namespace later changes from "global" to "local", we want this vsock > > > > > >>> + * to continue operating normally and not suddenly break. For that > > > > > >>> + * reason, we save the mode here and later use it when performing > > > > > >>> + * socket lookups with vsock_net_check_mode() (see vhost_vsock_get()). > > > > > >>> + */ > > > > > >>> + vsock->net_mode = vsock_net_mode(net); > > > > > >> > > > > > >> I'm sorry for the very late feedback. I think that at very least the > > > > > >> user-space needs a way to query if the given transport is in local or > > > > > >> global mode, as AFAICS there is no way to tell that when socket creation > > > > > >> races with mode change. > > > > > > > > > > > > Are you thinking something along the lines of sockopt? > > > > > > > > > > I'd like to see a way for the user-space to query the socket 'namespace > > > > > mode'. > > > > > > > > > > sockopt could be an option; a possibly better one could be sock_diag. Or > > > > > you could do both using dumping the info with a shared helper invoked by > > > > > both code paths, alike what TCP is doing. > > > > > >> Also I'm a bit uneasy with the model implemented here, as 'local' socket > > > > > >> may cross netns boundaris and connect to 'local' socket in other netns > > > > > >> (if I read correctly patch 2/12). That in turns AFAICS break the netns > > > > > >> isolation. > > > > > > > > > > > > Local mode sockets are unable to communicate with local mode (and global > > > > > > mode too) sockets that are in other namespaces. The key piece of code > > > > > > for that is vsock_net_check_mode(), where if either modes is local the > > > > > > namespaces must be the same. > > > > > > > > > > Sorry, I likely misread the large comment in patch 2: > > > > > > > > > > https://lore.kernel.org/netdev/20251126-vsock-vmtest-v12-2-257ee21cd5de@meta.com/ > > > > > > > > > > >> Have you considered instead a slightly different model, where the > > > > > >> local/global model is set in stone at netns creation time - alike what > > > > > >> /proc/sys/net/ipv4/tcp_child_ehash_entries is doing[1] - and > > > > > >> inter-netns connectivity is explicitly granted by the admin (I guess > > > > > >> you will need new transport operations for that)? > > > > > >> > > > > > >> /P > > > > > >> > > > > > >> [1] tcp allows using per-netns established socket lookup tables - as > > > > > >> opposed to the default global lookup table (even if match always takes > > > > > >> in account the netns obviously). The mentioned sysctl specify such > > > > > >> configuration for the children namespaces, if any. > > > > > > > > > > > > I'll save this discussion if the above doesn't resolve your concerns. > > > > > I still have some concern WRT the dynamic mode change after netns > > > > > creation. I fear some 'unsolvable' (or very hard to solve) race I can't > > > > > see now. A tcp_child_ehash_entries-like model will avoid completely the > > > > > issue, but I understand it would be a significant change over the > > > > > current status. > > > > > > > > > > "Luckily" the merge window is on us and we have some time to discuss. Do > > > > > you have a specific use-case for the ability to change the netns > > > > > mode > > > > > after creation? > > > > > > > > > > /P > > > > > > > > I don't think there is a hard requirement that the mode be change-able > > > > after creation. Though I'd love to avoid such a big change... or at > > > > least leave unchanged as much of what we've already reviewed as > > > > possible. > > > > > > > > In the scheme of defining the mode at creation and following the > > > > tcp_child_ehash_entries-ish model, what I'm imagining is: > > > > - /proc/sys/net/vsock/child_ns_mode can be set to "local" or "global" > > > > - /proc/sys/net/vsock/child_ns_mode is not immutable, can change any > > > > number of times > > > > > > > > - when a netns is created, the new netns mode is inherited from > > > > child_ns_mode, being assigned using something like: > > > > > > > > net->vsock.ns_mode = > > > > get_net_ns_by_pid(current->pid)->child_ns_mode > > > > > > > > - /proc/sys/net/vsock/ns_mode queries the current mode, returning > > > > "local" or "global", returning value of net->vsock.ns_mode > > > > - /proc/sys/net/vsock/ns_mode and net->vsock.ns_mode are immutable and > > > > reject writes > > > > > > > > Does that align with what you have in mind? > > > > > > Hey Paolo, I just wanted to sync up on this one. Does the above align > > > with what you envision? > > > > Hi Bobby, AFAIK Paolo was at LPC, so there could be some delay. > > > > FYI I'll be off from Dec 25 to Jan 6, so if we want to do an RFC in the > > middle, I'll do my best to take a look before my time off. > > > > Thanks, > > Stefano Just sent this out, though I acknowledge its pretty last minute WRT your time off. If I don't hear from you before then, have a good holiday! Best, Bobby