From: Jan Kara <jack@suse.cz>
To: <linux-fsdevel@vger.kernel.org>
Cc: <linux-mm@kvack.org>,
ocfs2-devel@lists.linux.dev,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Farhad Alemi <farhad.alemi@berkeley.edu>, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2] quota: Verify special quota formats match sb type
Date: Wed, 2 Sep 2026 15:36:58 +0200 [thread overview]
Message-ID: <20260902132458.23590-1-jack@suse.cz> (raw)
Hello,
there are certain quota formats that are created only for particular
filesystems - ocfs2 and tmpfs quota formats in particular. Make sure these
formats are indeed being enabled only for filesystem of appropriate type.
Otherwise quota format operations can easily crash as was spotted by fuzz
testing. The only gripe I have with this solution is the recognition of
filesystem type based on sb->s_type->name looks a bit hacky. Another way to do
this would be to directly compare against e.g. shmem_fs_type but that is a bit
cumbersome since struct file_system_type is generally declared in a relatively
narrow scope (not available where quota ops are implemented) so the filesystem
would need to provide a helper to compare against it. Let me know what people
prefer.
Once reviewed, I can merge these patches through my tree as they are only quota
related and very unlikely to clash with anything.
Honza
next reply other threads:[~2026-09-02 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 13:36 Jan Kara [this message]
2026-09-02 13:36 ` [PATCH 1/2] ocfs2: Refuse to enable ocfs2 format for another filesystem Jan Kara
2026-09-02 21:07 ` Mark Fasheh
2026-09-03 1:36 ` Joseph Qi
2026-09-02 13:37 ` [PATCH 2/2] shmem: Refuse to enable tmpfs " Jan Kara
2026-09-03 2:31 ` Hugh Dickins
2026-09-03 8:47 ` 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=20260902132458.23590-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=baolin.wang@linux.alibaba.com \
--cc=farhad.alemi@berkeley.edu \
--cc=hughd@google.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ocfs2-devel@lists.linux.dev \
/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