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. --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 > >
