All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: "Christian Brauner" <brauner@kernel.org>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	"Jan Kara" <jack@suse.cz>, "Jakub Kicinski" <kuba@kernel.org>,
	"Namjae Jeon" <linkinjeon@kernel.org>,
	"Hisam Mehboob" <hisamshar@gmail.com>,
	"Martin Kepplinger-Novaković" <martink@posteo.de>,
	"Amir Goldstein" <amir73il@gmail.com>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Eric Biggers" <ebiggers@kernel.org>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"David Howells" <dhowells@redhat.com>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Theodore Ts'o" <tytso@mit.edu>,
	"Catalin Iacob" <iacobcatalin@gmail.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Maciej W. Rozycki" <macro@orcam.me.uk>,
	"Andrei Vagin" <avagin@gmail.com>,
	"Wei Yang" <richard.weiyang@gmail.com>,
	"Bhavik Sachdev" <b.sachdev1904@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Wang Yan" <wangyan01@kylinos.cn>,
	Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>,
	"Malaya Kumar Rout" <malayarout91@gmail.com>,
	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" <enelsonmoore@gmail.com>,
	"Luis de Bethencourt" <luisbg@kernel.org>,
	"Salah Triki" <salah.triki@gmail.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Tigran A. Aivazian" <aivazian.tigran@gmail.com>,
	"Madhavan Srinivasan" <maddy@linux.ibm.com>,
	"Alexander Viro" <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] bfs: remove the filesystem
Date: Fri, 4 Sep 2026 17:06:19 +0100	[thread overview]
Message-ID: <aprr9xUwEmjA1N5T@gremlin> (raw)
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

  reply	other threads:[~2026-09-04 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04  8:29 [PATCH] bfs: remove the filesystem Ethan Nelson-Moore
2026-09-04  8:51 ` Tigran Aivazian
2026-09-04  9:15   ` Lorenzo Stoakes (ARM)
2026-09-04  9:55   ` Jan Kara
2026-09-04  9:59 ` Jan Kara
2026-09-04 10:05 ` Lorenzo Stoakes (ARM)
2026-09-04 10:18   ` Tigran Aivazian
2026-09-04 11:43     ` Lorenzo Stoakes (ARM)
2026-09-04 10:43 ` Christian Brauner
2026-09-04 15:10   ` Darrick J. Wong
2026-09-04 16:06     ` Lorenzo Stoakes (ARM) [this message]
2026-09-07  8:00     ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aprr9xUwEmjA1N5T@gremlin \
    --to=ljs@kernel.org \
    --cc=aivazian.tigran@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=avagin@gmail.com \
    --cc=b.sachdev1904@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=brauner@kernel.org \
    --cc=chleroy@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dhowells@redhat.com \
    --cc=djwong@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=enelsonmoore@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=hisamshar@gmail.com \
    --cc=iacobcatalin@gmail.com \
    --cc=jack@suse.cz \
    --cc=kuba@kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luisbg@kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=maddy@linux.ibm.com \
    --cc=malayarout91@gmail.com \
    --cc=martink@posteo.de \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=reddybalavignesh9979@gmail.com \
    --cc=richard.weiyang@gmail.com \
    --cc=salah.triki@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=stephen@networkplumber.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wangyan01@kylinos.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.