From: Ali Ahmet Memis <ali@iusegentoo.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>, Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: fs/ufs: three reviewed fixes looking for a tree
Date: Fri, 14 Aug 2026 08:36:53 +0000 [thread overview]
Message-ID: <20260814083655.919447-1-ali@iusegentoo.com> (raw)
Hi Christian,
I have three UFS fixes that Jan has reviewed, but they haven't been
picked up yet. I'm not quite sure which tree they should go through.
There isn't a separate MAINTAINERS entry for fs/ufs, and
get_maintainer.pl doesn't turn up much for files under it. I'm pinging
you since you've taken most of the recent UFS changes, but please let me
know if I should send these elsewhere.
ufs: create the root dentry after loading cylinder metadata
Cc: stable, Reviewed-by: Jan Kara
https://lore.kernel.org/all/20260801071306.59484-2-ali@iusegentoo.com/
ufs: validate cylinder group metadata before caching it
Cc: stable, Reviewed-by: Jan Kara
https://lore.kernel.org/all/20260801071306.59484-3-ali@iusegentoo.com/
ufs: do not treat unreadable directory blocks as empty
Reviewed-by: Jan Kara
https://lore.kernel.org/all/20260801013942.279992-1-ali@iusegentoo.com/
The first two fix a mount teardown NULL dereference and an out-of-bounds
access caused by on-disk cylinder group fields; both can be triggered by
a crafted filesystem image. The third fixes an rmdir case where an
unreadable directory block could cause a non-empty directory to be
treated as empty.
If useful, I can resend these as a small series with Jan's review tags
collected, or rebase them onto whichever tree you'd prefer.
I also have a larger series from Aug 1 that hasn't had any replies yet:
[PATCH 00/10] ufs: correctness fixes for valid on-disk filesystems
https://lore.kernel.org/all/20260801225530.148386-1-ali@iusegentoo.com/
That series is a bit different from the three above: the issues show up
on valid FreeBSD filesystems rather than crafted images. It includes a
symlink case that can read past the end of the device and panic on
unlink, a tail relocation bug that can corrupt data on 64 KiB pages,
and missing enforcement of on-disk immutable and append-only flags.
It's a larger review job, which is why I kept it separate. No rush on
the series as a whole, but there are a few fairly serious bugs in there.
Thanks,
Ali
reply other threads:[~2026-08-14 8:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260814083655.919447-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