mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuangpeng <shuangpeng.kernel@gmail.com>
To: Pedro Demarchi Gomes <pedrodemargomes@gmail.com>
Cc: ocfs2-devel@lists.linux.dev, mark@fasheh.com, jlbec@evilplan.org,
	joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ocfs2: slab-out-of-bounds in down_read_trylock from quota-on path
Date: Wed, 1 Apr 2026 16:36:42 -0400	[thread overview]
Message-ID: <20F9C447-2953-4028-B1F5-2CBE5580DAE8@gmail.com> (raw)
In-Reply-To: <ac0Buq9DS9kREZvt@fedora>

> 
> Hi Shuangpeng,
> 
> This looks like a quota format mismatch rather than an OCFS2 bug itself.
> 
> Your reproducer creates an F2FS image with quota format id = 3, which is
> specific to OCFS2. When quotactl() is issued, the following path is taken:
> 
> f2fs_quota_on
>  -> dquot_load_quota_inode
>      -> dquot_load_quota_sb
>          -> ocfs2_local_check_quota_file
> 
> Inside dquot_load_quota_sb(), find_quota_format(id) resolves the format based
> solely on the on-disk id. Since id = 3 corresponds to ocfs2_quota_format, the
> quota subsystem ends up invoking OCFS2-specific handlers on an F2FS inode.
> 
> So the root cause is that the quota framework does not validate whether the
> quota format is compatible with the filesystem.

Thank you for the clarification. In that case, do you think it would make sense for
me to CC the quota subsystem in the follow-up?

      reply	other threads:[~2026-04-01 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 19:15 Shuangpeng
2026-04-01 12:06 ` Pedro Demarchi Gomes
2026-04-01 20:36   ` Shuangpeng [this message]

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=20F9C447-2953-4028-B1F5-2CBE5580DAE8@gmail.com \
    --to=shuangpeng.kernel@gmail.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=pedrodemargomes@gmail.com \
    /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®