From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Jiakai Xu <xujiakai24@mails.ucas.ac.cn>,
linux-kernel@vger.kernel.org, ocfs2-devel@lists.linux.dev
Cc: Joel Becker <jlbec@evilplan.org>,
Kurt Hackel <kurt.hackel@oracle.com>,
Mark Fasheh <mark@fasheh.com>, Heming Zhao <heming.zhao@suse.com>
Subject: Re: [PATCH] ocfs2: fix use-after-free in ocfs2_inode_lock_full_nested during unmount
Date: Fri, 8 May 2026 17:47:54 +0800 [thread overview]
Message-ID: <75570681-a25a-4cec-9874-b76fec6167e8@linux.alibaba.com> (raw)
In-Reply-To: <20260508060107.2666033-1-xujiakai24@mails.ucas.ac.cn>
On 5/8/26 2:01 PM, Jiakai Xu wrote:
> A race condition exists between filesystem unmount and inode permission
> operations. When ocfs2_dismount_volume() frees the ocfs2_super (osb)
> structure, concurrent access via OCFS2_SB(inode->i_sb) in
> ocfs2_inode_lock_full_nested() can dereference freed memory, causing a
> page fault in __pv_queued_spin_lock_slowpath via
> ocfs2_is_hard_readonly() -> spin_lock(&osb->osb_lock).
>
> Fix this with two changes:
>
> 1. In ocfs2_dismount_volume(): set sb->s_fs_info = NULL before
> kfree(osb), so OCFS2_SB() returns NULL instead of a dangling pointer
> during the teardown race window.
>
> 2. In ocfs2_inode_lock_full_nested(): add a NULL check on osb after
> OCFS2_SB(), returning -EIO if the superblock info is already gone.
> This ensures the crash path is handled gracefully when the
> filesystem is being torn down.
>
It seems this is not enough, or TOCTOU still exists. Say:
Thread A Thread B
osb = OCFS2_SB(inode->i_sb)
ocfs2_dismount_volume()
-> sb->s_fs_info = NULL
-> kfree(osb)
use freed osb
BTW, how did you find this issue?
Joseph
> Signed-off-by: Jiakai Xu <xujiakai24@mails.ucas.ac.cn>
> Fixes: ccd979bdbce9f ("OCFS2: The Second Oracle Cluster Filesystem")
> ---
> fs/ocfs2/dlmglue.c | 3 +++
> fs/ocfs2/super.c | 2 +-
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/dlmglue.c b/fs/ocfs2/dlmglue.c
> index 7283bb2c5a31..cd619958a0a2 100644
> --- a/fs/ocfs2/dlmglue.c
> +++ b/fs/ocfs2/dlmglue.c
> @@ -2435,6 +2435,9 @@ int ocfs2_inode_lock_full_nested(struct inode *inode,
> struct ocfs2_super *osb = OCFS2_SB(inode->i_sb);
> struct buffer_head *local_bh = NULL;
>
> + if (!osb)
> + return -EIO;
> +
> mlog(0, "inode %llu, take %s META lock\n",
> (unsigned long long)OCFS2_I(inode)->ip_blkno,
> ex ? "EXMODE" : "PRMODE");
> diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
> index b875f01c9756..3fd56638e4f0 100644
> --- a/fs/ocfs2/super.c
> +++ b/fs/ocfs2/super.c
> @@ -1881,10 +1881,10 @@ static void ocfs2_dismount_volume(struct super_block *sb, int mnt_err)
> printk(KERN_INFO "ocfs2: Unmounting device (%s) on (node %s)\n",
> osb->dev_str, nodestr);
>
> + sb->s_fs_info = NULL;
> ocfs2_delete_osb(osb);
> kfree(osb);
> sb->s_dev = 0;
> - sb->s_fs_info = NULL;
> }
>
> static int ocfs2_setup_osb_uuid(struct ocfs2_super *osb, const unsigned char *uuid,
next prev parent reply other threads:[~2026-05-08 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 6:01 [PATCH] ocfs2: fix use-after-free in ocfs2_inode_lock_full_nested during unmount Jiakai Xu
2026-05-08 9:47 ` Joseph Qi [this message]
2026-05-09 4:28 ` Jiakai Xu
2026-05-09 6:20 ` Joseph Qi
2026-05-09 8:46 ` Jiakai Xu
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=75570681-a25a-4cec-9874-b76fec6167e8@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=xujiakai24@mails.ucas.ac.cn \
/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