From: "Darrick J. Wong" <djwong@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] sysv: Remove the filesystem
Date: Mon, 6 Jan 2025 15:31:12 -0800 [thread overview]
Message-ID: <20250106233112.GI6156@frogsfrogsfrogs> (raw)
In-Reply-To: <b4a292ba5a33cc5d265a46824057fe001ed2ced6.camel@kernel.org>
On Mon, Jan 06, 2025 at 02:52:11PM -0500, Jeff Layton wrote:
> On Mon, 2025-01-06 at 17:24 +0100, Jan Kara wrote:
> > Since 2002 (change "Replace BKL for chain locking with sysvfs-private
> > rwlock") the sysv filesystem was doing IO under a rwlock in its
> > get_block() function (yes, a non-sleepable lock hold over a function
> > used to read inode metadata for all reads and writes). Nobody noticed
> > until syzbot in 2023 [1]. This shows nobody is using the filesystem.
> > Just drop it.
> >
> > [1] https://lore.kernel.org/all/0000000000000ccf9a05ee84f5b0@google.com/
> >
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> > What do people think about this? Or should we perhaps go through a (short)
> > deprecation period where we warn about removal?
> >
>
> FWIW, it was orphaned in 2023:
>
> commit a8cd2990b694ed2c0ef0e8fc80686c664b4ebbe5
> Author: Christoph Hellwig <hch@lst.de>
> Date: Thu Feb 16 07:29:22 2023 +0100
>
> orphan sysvfs
>
> This code has been stale for years and I have no way to test it.
>
>
> Given how long this was broken with no one noticing, and since it's not
> being adequately tested, I vote we remove it.
I concur, if someone really wants this we can always add it back (after
making them deal with the bugs):
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
>
> Reviewed-by: Jeff Layton <jlayton@kernel.org>
>
next prev parent reply other threads:[~2025-01-06 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 16:24 [PATCH] sysv: Remove the filesystem Jan Kara
2025-01-06 19:52 ` Jeff Layton
2025-01-06 23:31 ` Darrick J. Wong [this message]
2025-01-07 7:17 ` Cedric Blancher
2025-01-07 10:08 ` Jan Kara
2025-01-07 15:13 ` Al Viro
2025-01-06 20:41 ` Matthew Wilcox
2025-01-07 14:35 ` Christian Brauner
2025-01-08 22:32 ` Bill O'Donnell
2025-01-09 15:05 ` Christian Brauner
2025-01-09 23:08 ` Bill O'Donnell
-- strict thread matches above, loose matches on Subject: below --
2025-02-20 16:39 Jan Kara
2025-02-20 18:50 ` Darrick J. Wong
2025-02-20 20:06 ` Jeff Layton
2025-02-21 9:38 ` Christian Brauner
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=20250106233112.GI6156@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@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 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.