mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Breno Rodrigues Alves <breno3011alves@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 0/1] fs: remove hpfs filesystem
Date: Fri, 23 Oct 2026 21:39:35 +0200 (CEST)	[thread overview]
Message-ID: <39b3990b-fed4-4b45-8819-88938901e57c@redhat.com> (raw)
In-Reply-To: <20261023151850.96475-1-breno3011alves@gmail.com>

Hi

I am still using HPFS. I have some data on it that I share with OS/2.


On Fri, 23 Oct 2026, Breno Rodrigues Alves wrote:

> The HPFS filesystem driver has been orphaned and unmaintained for a
> long time.  An RFC on linux-fsdevel stated that HPFS is about to be
> removed as it has no remaining users and is no longer supported on
> SMP or PREEMPT kernels.

This was a problem back in the kernels 2.6.*. I fixed it long time ago 
(see the commit 7dd29d8d865efdb00c0542a5d2c87af8c52ea6c7 and the merge 
7f4238a0ef8858e1f9b02a874b5818f6e9846673).

I am using it with SMP and PREEMPT, it does nothing weird. It just locks 
everything with a per-filesystem mutex.

> Recent vulnerabilities (e.g.,
> CVE-2026-97486) further highlight the lack of maintenance.

This is a regular bug, not a security bug. You can't gain unauthorized 
access throught this.

Mikulas


> This patch removes the driver along with its Kconfig entry,
> documentation, and CREDITS entries.  The HPFS_SUPER_MAGIC value in
> include/uapi/linux/magic.h is kept for userspace ABI compatibility,
> and defconfig cleanups will be sent separately to the respective
> architecture maintainers.
> 
> Breno Rodrigues Alves (1):
>   fs: remove hpfs filesystem
> 
>  CREDITS                             |    2 -
>  Documentation/filesystems/hpfs.rst  |  353 ---------
>  Documentation/filesystems/index.rst |    1 -
>  MAINTAINERS                         |    6 -
>  fs/Kconfig                          |    1 -
>  fs/Makefile                         |    1 -
>  fs/hpfs/Kconfig                     |   17 -
>  fs/hpfs/Makefile                    |    9 -
>  fs/hpfs/alloc.c                     |  582 --------------
>  fs/hpfs/anode.c                     |  498 ------------
>  fs/hpfs/buffer.c                    |  232 ------
>  fs/hpfs/dentry.c                    |   62 --
>  fs/hpfs/dir.c                       |  331 --------
>  fs/hpfs/dnode.c                     | 1095 ---------------------------
>  fs/hpfs/ea.c                        |  368 ---------
>  fs/hpfs/file.c                      |  276 -------
>  fs/hpfs/hpfs.h                      |  579 --------------
>  fs/hpfs/hpfs_fn.h                   |  379 ---------
>  fs/hpfs/inode.c                     |  318 --------
>  fs/hpfs/map.c                       |  335 --------
>  fs/hpfs/name.c                      |  114 ---
>  fs/hpfs/namei.c                     |  621 ---------------
>  fs/hpfs/super.c                     |  789 -------------------
>  23 files changed, 6969 deletions(-)
>  delete mode 100644 Documentation/filesystems/hpfs.rst
>  delete mode 100644 fs/hpfs/Kconfig
>  delete mode 100644 fs/hpfs/Makefile
>  delete mode 100644 fs/hpfs/alloc.c
>  delete mode 100644 fs/hpfs/anode.c
>  delete mode 100644 fs/hpfs/buffer.c
>  delete mode 100644 fs/hpfs/dentry.c
>  delete mode 100644 fs/hpfs/dir.c
>  delete mode 100644 fs/hpfs/dnode.c
>  delete mode 100644 fs/hpfs/ea.c
>  delete mode 100644 fs/hpfs/file.c
>  delete mode 100644 fs/hpfs/hpfs.h
>  delete mode 100644 fs/hpfs/hpfs_fn.h
>  delete mode 100644 fs/hpfs/inode.c
>  delete mode 100644 fs/hpfs/map.c
>  delete mode 100644 fs/hpfs/name.c
>  delete mode 100644 fs/hpfs/namei.c
>  delete mode 100644 fs/hpfs/super.c
> 
> -- 
> 2.56.0
> 


      parent reply	other threads:[~2026-10-23 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 15:18 Breno Rodrigues Alves
2026-10-23 15:18 ` [PATCH 1/1] " Breno Rodrigues Alves
2026-10-23 19:39 ` Mikulas Patocka [this message]

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=39b3990b-fed4-4b45-8819-88938901e57c@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=breno3011alves@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®