From: Ali Ahmet Memis <ali@iusegentoo.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add myself as UFS filesystem maintainer
Date: Sat, 1 Aug 2026 10:30:59 +0300 [thread overview]
Message-ID: <20260801073059.63651-1-ali@iusegentoo.com> (raw)
In-Reply-To: <am10yuQx5a3h2pXH@casper.infradead.org>
On Sat, Aug 01, 2026 at 05:23:38AM +0100, Matthew Wilcox wrote:
> Convince us you aren't Jia Tan. You have almost no history with the
> Linux kernel (one commit that I can find, and that has a different email
> address attached to it).
Fair question, and after xz it is the right one to ask, so no offence
taken.
Proving a negative is hard, so here is what I can actually show.
The commit you found is 607af438e643 ("tools/power/x86/
intel-speed-select: Harden daemon pidfile open"). I wrote it as Ali
Ahmet MEMIS <dev@unknownbbqr.xyz> and Srinivas Pandruvada applied it. I
still control that address and will confirm from it that
ali@iusegentoo.com is the same person if that is useful. I have moved my
kernel work to the iusegentoo.com address and will keep to one from here.
Past that, I would rather be judged on this week's work than on my word:
- ufs: do not treat unreadable directory blocks as empty (rmdir data
loss)
- ufs: free the buffer head container in ubh_bforget (Luis Henriques
posted this fix in 2018 and it was never applied)
- reviews of the pending cgsize and cssize hardening patches
- a two patch hardening series with KASAN reproducers, for a mount
teardown NULL deref and an out of bounds write driven by on-disk
cg_cgx
On the entry: point taken, adding myself as Maintained on this much
history is premature. Consider this patch dropped. I will keep sending
fixes and reviews, and if an entry ever looks warranted to you and the
other reviewers we can revisit it then. The fixes do not depend on it.
What I care about is ufs bugs not being ignored. If routing my fixes
through you or the vfs tree is the better path, that is fine by me.
next prev parent reply other threads:[~2026-08-01 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 2:50 Ali Ahmet Memis
2026-08-01 4:23 ` Matthew Wilcox
2026-08-01 7:30 ` Ali Ahmet Memis [this message]
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=20260801073059.63651-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 \
--cc=willy@infradead.org \
/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®