From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pf1-f178.google.com (mail-pf1-f178.google.com [209.85.210.178]) (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 E5CB833C523 for ; Tue, 21 Oct 2025 14:34:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.178 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761057298; cv=none; b=aPs5CQw0FkAMSuEtNwLiXXFVkm4dK61GL/Ct9p/7Ue0zdiVQ7pap4ynxLCR/RZ8Y2LXvveCDM6NKF54Zb8n64PFP4foqqPI0AbKMmkMVlBVTzsIb8zeZA3RGuvG4OWTrpORAIJD8uC1N0H+ld1hBwfj9zFwQPZUSEAg0EzhZAcU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761057298; c=relaxed/simple; bh=HtEYm3WbJmCN1KO4SaCrajhVynmFoIbWwbCW53lJb9o=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=eQJ6wfhcbtiG8vMAzGaKbONZOLpi0mBWF5ye0strS6RVxnwq3j3EK4g4LP549TgaakYVGCnFAraxpMcDfI3WiYfohVwkFG2CPSBgC8IHaTt3YKYlZ5b3877KPboBIYPI5fiUquJIDkkX33EHg0IX0jOOZCDe/2Hu7ZWyTcbK8WA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=toxicpanda.com; spf=pass smtp.mailfrom=toxicpanda.com; dkim=pass (2048-bit key) header.d=toxicpanda.com header.i=@toxicpanda.com header.b=dbM54z7X; arc=none smtp.client-ip=209.85.210.178 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=toxicpanda.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=toxicpanda.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=toxicpanda.com header.i=@toxicpanda.com header.b="dbM54z7X" Received: by mail-pf1-f178.google.com with SMTP id d2e1a72fcca58-781010ff051so4223280b3a.0 for ; Tue, 21 Oct 2025 07:34:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toxicpanda.com; s=google; t=1761057296; x=1761662096; 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=sV3KIhc1PNPd/uW7bqfRoDcwumTG1e/maPgTaMLXuW0=; b=dbM54z7X73YK0xvaCLxSrxd7B9cDEkxGaKXjhj2zmoGu16KWr+T0FJK0jdTCmpGsH3 o4ZFBsyVFrLggPOL/Tb6YvsfQTfHNlVgGYcqpMvgqE3j8e7S6SI6xyRSgNdyKRk9vffD sG4J8Ir0DyDNcILEwSnSyWufpvhezNY11r2M0ghYMIFt6G5EvBatBtUx8e2wYZJ0ygHZ C9N17nDus6p3E1Up4CMOr7as/cWtYPTBpPBD5RhcB+Cl5nIfnA0qqH4EZ1dT09I29LSO ZEh8Ip1rrYdkvUAX71vHOoUZMNBDX8rajGm7vagcak1T0w/X1gfLdGtEmchGigMrqEWX /mlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761057296; x=1761662096; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=sV3KIhc1PNPd/uW7bqfRoDcwumTG1e/maPgTaMLXuW0=; b=ikz4NuUEmhDCr+qN2Q2gzk2UDL20+ccc4pTDQ4kxcbO+/iS0QNggGE7MeObyBgbWtL /G1n4gqu2yQyqBQbkVFztC9B+/lSzvHukEWY8P6wEOLqC+cDqZ47OJ/ufAHXgqNp+vnt xBnmXgB9drUtsEI9Wh8vp8npHZiyG9bS1CQeqO20CVBL3alzYjr4RpcYFhuo+4O1TLK0 6hFZEnEULI10wyxiXG71TbyDrEr8PxxFGwZMBqjh/1rikOSL//QFYv4CTAaIUCggLEls Z5MUPJHzSc0KMxo9VrqC8U8myY9juQh54gLEUJh+IakZmFmEcYiFdt3jaSLa7UhemBfa eAoQ== X-Forwarded-Encrypted: i=1; AJvYcCXkFuqHOQzXXvbHmagtpTFdC02U1iN+TJhrAGl6OZyUk9Lz/qYRcSFwiqmsZRti5CzilOQAdM6mlElGXdw=@vger.kernel.org X-Gm-Message-State: AOJu0YzUs7jecQAjcr8dTfgFVJZnL48cKRe0XJ8TTryBx+RCmjLuUVlG fa70E5PLM0A7jC2MzfVcPEZXQD1ikp8K8QUUyDmNsYC1AvD1Xxn2gDKqdvOyOuJJoOM= X-Gm-Gg: ASbGncuyLb0du+OMWXwGaap8jtlKjR748JhSSTfNczh5Ok/swwsxbZQkbF3ruklHwxL ki4ysKlHbQsKINvkk/zb/4mDwGH2QfizNf75Bxtb8oyYKDKUiCqF0y66qrfALYsUm3dp23migYc XIZNfpj7Z3c2m+7Mv0WYlNPzpIl5flbAxtHcQOBc4MzS6SLmBd9K+qTY8smXbj9ARrq4oUSi4cH aIolcKkIa3vdYHlsuh4kTMyAEFrPPIRFSBt1nmh0NaJSADzIRyxIV8zVy9cx10Zu0Ex5QVS2eCr fwU5JZWbmwWfVMZRA1osmg0jiL7evL44lDrN29BdsOS07WO03ujHmTmgVn4slZZZo0nXnKwgvEP 9Ci32bUULebB9w5YwspUPMkDl0BA3YG401MW1x5t3U7iCT6dx2ekv5E2VaHtxcX+bjbxcHEoNt5 6YuF3h97No X-Google-Smtp-Source: AGHT+IHBX9TIE3IQtEBoV7LOteBO6V2Q79FbArZ4HOehhBp5RxecJgOwYxXXdgG5tSXjdbgoVNEnFA== X-Received: by 2002:a05:6a00:4b0f:b0:781:275a:29d9 with SMTP id d2e1a72fcca58-7a220b10725mr23389331b3a.18.1761057296233; Tue, 21 Oct 2025 07:34:56 -0700 (PDT) Received: from localhost ([12.197.85.234]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7a22ff15829sm11500038b3a.11.2025.10.21.07.34.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Oct 2025 07:34:54 -0700 (PDT) Date: Tue, 21 Oct 2025 10:34:54 -0400 From: Josef Bacik To: Christian Brauner Cc: linux-fsdevel@vger.kernel.org, Jeff Layton , Jann Horn , Mike Yuan , Zbigniew =?utf-8?Q?J=C4=99drzejewski-Szmek?= , Lennart Poettering , Daan De Meyer , Aleksa Sarai , Amir Goldstein , Tejun Heo , Johannes Weiner , Thomas Gleixner , Alexander Viro , Jan Kara , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, bpf@vger.kernel.org, Eric Dumazet , Jakub Kicinski , netdev@vger.kernel.org, Arnd Bergmann Subject: Re: [PATCH RFC DRAFT 00/50] nstree: listns() Message-ID: <20251021143454.GA8072@fedora> References: <20251021-work-namespace-nstree-listns-v1-0-ad44261a8a5b@kernel.org> 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: <20251021-work-namespace-nstree-listns-v1-0-ad44261a8a5b@kernel.org> On Tue, Oct 21, 2025 at 01:43:06PM +0200, Christian Brauner wrote: > Hey, > > As announced a while ago this is the next step building on the nstree > work from prior cycles. There's a bunch of fixes and semantic cleanups > in here and a ton of tests. > > I need helper here!: Consider the following current design: > > Currently listns() is relying on active namespace reference counts which > are introduced alongside this series. > > The active reference count of a namespace consists of the live tasks > that make use of this namespace and any namespace file descriptors that > explicitly pin the namespace. > > Once all tasks making use of this namespace have exited or reaped, all > namespace file descriptors for that namespace have been closed and all > bind-mounts for that namespace unmounted it ceases to appear in the > listns() output. > > My reason for introducing the active reference count was that namespaces > might obviously still be pinned internally for various reasons. For > example the user namespace might still be pinned because there are still > open files that have stashed the openers credentials in file->f_cred, or > the last reference might be put with an rcu delay keeping that namespace > active on the namespace lists. > > But one particularly strange example is CONFIG_MMU_LAZY_TLB_REFCOUNT=y. > Various architectures support the CONFIG_MMU_LAZY_TLB_REFCOUNT option > which uses lazy TLB destruction. > > When this option is set a userspace task's struct mm_struct may be used > for kernel threads such as the idle task and will only be destroyed once > the cpu's runqueue switches back to another task. So the kernel thread > will take a reference on the struct mm_struct pinning it. > > And for ptrace() based access checks struct mm_struct stashes the user > namespace of the task that struct mm_struct belonged to originally and > thus takes a reference to the users namespace and pins it. > > So on an idle system such user namespaces can be persisted for pretty > arbitrary amounts of time via struct mm_struct. > > Now, without the active reference count regulating visibility all > namespace that still are pinned in some way on the system will appear in > the listns() output and can be reopened using namespace file handles. > > Of course that requires suitable privileges and it's not really a > concern per se because a task could've also persist the namespace > recorded in struct mm_struct explicitly and then the idle task would > still reuse that struct mm_struct and another task could still happily > setns() to it afaict and reuse it for something else. > > The active reference count though has drawbacks itself. Namely that > socket files break the assumption that namespaces can only be opened if > there's either live processes pinning the namespace or there are file > descriptors open that pin the namespace itself as the socket SIOCGSKNS > ioctl() can be used to open a network namespace based on a socket which > only indirectly pins a network namespace. > > So that punches a whole in the active reference count tracking. So this > will have to be handled as right now socket file descriptors that pin a > network namespace that don't have an active reference anymore (no live > processes, not explicit persistence via namespace fds) can't be used to > issue a SIOCGSKNS ioctl() to open the associated network namespace. > > So two options I see if the api is based on ids: > > (1) We use the active reference count and somehow also make it work with > sockets. > (2) The active reference count is not needed and we say that listns() is > an introspection system call anyway so we just always list > namespaces regardless of why they are still pinned: files, > mm_struct, network devices, everything is fair game. > (3) Throw hands up in the air and just not do it. > I think the active reference counts are just nice to have, if I'm not missing something we still have to figure out which pid is using the namespace we may want to enter, so there's already a "time of check, time of use" issue. I think if we want to have the active count we can do it just as an advisory thing, have a flag that says "this ns is dying and you can't do anything with it", and then for network namespaces we can just never set the flag and let the existing SIOCKGSNS ioctl work as is. The bigger question (and sorry I didn't think about this before now), is how are we going to integrate this into the rest of the NS related syscalls? Having progromatic introspection is excellent from a usabiility point of view, but we also want to be able to have an easy way to get a PID from these namespaces, and even eventually do things like setns() based on these IDs. Those are followup series of course, but we should at least have a plan for them. Thanks, Josef