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 v2 0/2] quota: Verify special quota formats match sb type
Date: Thu, 3 Sep 2026 11:05:03 +0200 [thread overview]
Message-ID: <20260903090053.13120-1-jack@suse.cz> (raw)
Hello,
here is v2 of the patches for fix quota crashes when quota format doesn't match
filesystem type. I'm now using s_magic instead of s_type for superblock type
checking as Hugh pointed out (thus I also didn't pick up OCFS2 guys' R-b tags
because the patch is different now). Once reviewed, I can merge these patches
through my tree as they are only quota related and very unlikely to clash with
anything.
Changes since v1:
* Use s_magic instead of s_type for superblock type checking
Original cover letter:
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.
Honza
Previous versions:
Link: http://lore.kernel.org/r/20260902132458.23590-1-jack@suse.cz # v1
next reply other threads:[~2026-09-03 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 9:05 Jan Kara [this message]
2026-09-03 9:05 ` [PATCH v2 1/2] ocfs2: Refuse to enable ocfs2 format for another filesystem Jan Kara
2026-09-03 10:15 ` Joseph Qi
2026-09-03 9:05 ` [PATCH v2 2/2] shmem: Refuse to enable tmpfs " Jan Kara
2026-09-03 15:15 ` Hugh Dickins
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=20260903090053.13120-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