mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ali Ahmet Memis <ali@iusegentoo.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] MAINTAINERS: add myself as UFS filesystem maintainer
Date: Sat,  1 Aug 2026 05:50:15 +0300	[thread overview]
Message-ID: <20260801025030.14178-1-ali@iusegentoo.com> (raw)

fs/ufs has no MAINTAINERS entry. get_maintainer.pl returns only the open
lists, so patches for it have no clear reviewer and tend to sit
unanswered. The archives show the cost of this: a truncate path memory
leak fix was posted in 2018 with a stable tag and was never applied [1],
and recent mount path hardening patches went weeks without a maintainer
to review or apply them [2][3].

The code needs attention. It parses on-disk BSD and Solaris layouts with
very little validation, so several crafted-image mount crashes are still
open. I have been reading it and fixing real bugs in the normal paths as
well, including the 2018 leak above and an rmdir path that treated an
unreadable directory block as empty and could drop a non-empty directory
[4].

I am willing to take responsibility for fs/ufs: review incoming patches,
carry the pending fixes, and keep it building and correct. Add a
Maintained entry to reflect that.

Link: https://lore.kernel.org/all/20180705150415.25070-1-lhenriques@suse.com/ [1]
Link: https://lore.kernel.org/all/20260717104033.38574-1-david.lee@trailofbits.com/ [2]
Link: https://lore.kernel.org/all/20260701215700.822003-1-kudo3228@gmail.com/ [3]
Link: https://lore.kernel.org/all/20260801013942.279992-1-ali@iusegentoo.com/ [4]
Signed-off-by: Ali Ahmet Memis <ali@iusegentoo.com>
---
 MAINTAINERS | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 62d53465e..8a1dc78f0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -27663,6 +27663,12 @@ L:	linux-input@vger.kernel.org
 S:	Maintained
 F:	drivers/hid/hid-udraw-ps3.c
 
+UFS FILESYSTEM
+M:	Ali Ahmet Memis <ali@iusegentoo.com>
+L:	linux-fsdevel@vger.kernel.org
+S:	Maintained
+F:	fs/ufs/
+
 UHID USERSPACE HID IO DRIVER
 M:	David Rheinsberg <david@readahead.eu>
 L:	linux-input@vger.kernel.org
-- 
2.54.0


             reply	other threads:[~2026-08-01  2:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01  2:50 Ali Ahmet Memis [this message]
2026-08-01  4:23 ` Matthew Wilcox
2026-08-01  7:30   ` Ali Ahmet Memis
2026-08-03  8:57     ` Jan Kara
2026-08-03  9:44       ` Ali Ahmet Memis
2026-08-03 10: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=20260801025030.14178-1-ali@iusegentoo.com \
    --to=ali@iusegentoo.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --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®