From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6F5CB3ACA4B; Fri, 4 Sep 2026 16:06:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788538000; cv=none; b=XW5XykRisGHZRhH++zFFu45/uCMdNC5LlXpa0D+P8l2zY9nVJxMw1fn9HX/6jeMW/ZpF/jSMenK1Oml8Q13y8tDjW6vKDiM6CV1nh9NTC4La3D7Z2vhA80neU6m756ybRoIDiyaKeo7rD/Vu4uLN8VwN0dhhxyT5Ip77hcldpRI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788538000; c=relaxed/simple; bh=8FSb/gjuciMqhZIT4RXlFvIKNcHmDi84w1BldFvuDhY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Sh/qN0alBc0a63zT/HPfMMRa4x3ha6j7NVeMS2us1rZ6NZfxV5Ip5df1wjlyySXZqLcyilEEGIShWyCgM9YWeEQu5sE5sTEv9ZQ6TVD/BGpYCNhb5jNG0omKeiuWapAkcV+BoXAq9ZyhlDAJdKaZUDfqxcfLplEB1ix+yjSH63Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=CFVs81Nr; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CFVs81Nr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2B31E1F00A3D; Fri, 4 Sep 2026 16:06:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1788537990; bh=89DU0GapqiOZlaA7jU9CQs5/T4ZZ4b0KeYVQAFryc+c=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=CFVs81Nrix1xWs3kup1P05Krc0JJYYhS/ViPHckidBWbZUUGJsinV0OpG0P2Yp0BM Yi+nMeESljaXeDglpK+m7DNQxDrSYy8UGDgOQoERJShk9RAc41+SjMQlXp7YkTY/cs KX7Zc2qg+zrln15rB1FL9dhfPpQNrATWQEC0mVvJPFKr8EUGnQG1Al5bkXiPq+CkAV 8ASReE6E/YXuMju48gmLyNRm35+cwsjDqveHmTZAEelBBwGoMRCiXvPw2ZAyXgeW7s FNu/myp6GFkUNY3kus7xr2P0HhWcShI8J6dlb8+vBIMclZAmORFzAg8TXYBEMMFa6n RwUUxSxh+CnkA== Date: Fri, 4 Sep 2026 17:06:19 +0100 From: "Lorenzo Stoakes (ARM)" To: "Darrick J. Wong" Cc: Christian Brauner , Shuah Khan , Randy Dunlap , Michael Ellerman , Nicholas Piggin , "Christophe Leroy (CS GROUP)" , Jan Kara , Jakub Kicinski , Namjae Jeon , Hisam Mehboob , Martin =?utf-8?Q?Kepplinger-Novakovi=C4=87?= , Amir Goldstein , Bagas Sanjaya , Eric Biggers , Geert Uytterhoeven , David Howells , Thomas Bogendoerfer , Theodore Ts'o , Catalin Iacob , Stephen Hemminger , Andrew Lunn , "Maciej W. Rozycki" , Andrei Vagin , Wei Yang , Bhavik Sachdev , Andrew Morton , Wang Yan , Bala-Vignesh-Reddy , Malaya Kumar Rout , linux-doc@vger.kernel.org, linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org, Ethan Nelson-Moore , Luis de Bethencourt , Salah Triki , Jonathan Corbet , "Tigran A. Aivazian" , Madhavan Srinivasan , Alexander Viro Subject: Re: [PATCH] bfs: remove the filesystem Message-ID: References: <20260904082954.48738-1-enelsonmoore@gmail.com> <20260904-hinnimmt-triumphieren-handgefertigt-4e51fe2ed659@brauner> <20260904151054.GG6047@frogsfrogsfrogs> Precedence: bulk X-Mailing-List: linux-kselftest@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: <20260904151054.GG6047@frogsfrogsfrogs> On Fri, Sep 04, 2026 at 08:10:54AM -0700, Darrick J. Wong wrote: > On Fri, Sep 04, 2026 at 12:43:09PM +0200, Christian Brauner wrote: > > On Fri, 04 Sep 2026 01:29:19 -0700, Ethan Nelson-Moore wrote: > > > bfs: remove the filesystem > > > > I agree. > > At the moment, I don't. Nowhere in this thread does anyone mention what > someone with a B(oot)FS filesystem image should do if they want to > extract whatever's stored in the filesystem. Are there userspace tools > for that purpose (ala efs)? Does "binwalk -e $bfs_image" suffice for > that purpose? Or is there solid evidence that there isn't even a single > user (ala freevxfs) who strongly wants it to stay in? > > I'm all for getting rid of old cruft but there still needs to be a > documented offramp for users. Use an older/downstream version of linux? :) It's like the museum piece arch stuff - people argue vigorously in favour of nommu (which btw is a variety of linux that _doesn't implement forking_ :))) gesticulating at talks given at conferences etc. But then never quite answer the 'why not use an older version of linux' or 'why not just maintain it downstraem for the 3 people who need it'. Also worth consider what the Venn diagram overlap of bfs users and people running even-vaguely-tip kernels/likely to ever upgrade is. Quite likely zero I expect? I get the desire not to lose people their data, but the code's not gone away forever :) > > --D > > > --- > > > > Applied to the vfs-7.4.bfs branch of the vfs/vfs.git tree. > > Patches in the vfs-7.4.bfs branch should appear in linux-next soon. > > > > Please report any outstanding bugs that were missed during review in a > > new review to the original patch series allowing us to drop it. > > > > It's encouraged to provide Acked-bys and Reviewed-bys even though the > > patch has now been applied. If possible patch trailers will be updated. > > > > Note that commit hashes shown below are subject to change due to rebase, > > trailer updates or similar. If in doubt, please check the listed branch. > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git > > branch: vfs-7.4.bfs > > > > [1/1] bfs: remove the filesystem > > https://git.kernel.org/vfs/vfs/c/e36781a626b2 > > > > -- Cheers, Lorenzo