mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Binbin Deng <18983559317@163.com>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v1] xfs: set healthmon mount cookie before publishing it
Date: Thu, 15 Oct 2026 07:38:07 -0700	[thread overview]
Message-ID: <20261015143807.GN2705364@frogsfrogsfrogs> (raw)
In-Reply-To: <20261015080225.45215-1-18983559317@163.com>

On Thu, Oct 15, 2026 at 04:02:25PM +0800, Binbin Deng wrote:
> xfs_ioc_health_monitor() allocates the healthmon object with kzalloc(), so
> mount_cookie starts as zero.  zero is also DETACHED_MOUNT_COOKIE, but
> xfs_healthmon_attach() publishes hm through mp->m_healthmon before storing
> the mount cookie.  A concurrent reporter can therefore acquire hm from
> xfs_healthmon_get(), see the detached cookie in xfs_healthmon_push(), and
> drop the event even though the monitor is being attached.
> 
> This is reachable by racing XFS_IOC_HEALTH_MONITOR with an operation
> that reports a health event, such as a filesystem shutdown.  Initialize
> the mount cookie before making hm visible through the RCU pointer so
> reporters always observe an attached monitor.
> 
> Found during a static-analysis-assisted audit: candidate sites were
> surfaced by a Coccinelle rule, and the reader/writer paths were
> confirmed by LLM-assisted (GLM-5.3) code inspection.  The issue was
> not observed at runtime; it is identified by code inspection only.
> 
> Fixes: a48373e7d35a ("xfs: start creating infrastructure for health monitoring")
> Cc: stable@vger.kernel.org

Cc: <stable@vger.kernel.org> # v7.0

> Signed-off-by: Binbin Deng <18983559317@163.com>

Yes, we should set the mount cookie before exposing hm to the world.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  fs/xfs/xfs_healthmon.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/xfs_healthmon.c b/fs/xfs/xfs_healthmon.c
> index 2bdd747f1ead..05d6f0494139 100644
> --- a/fs/xfs/xfs_healthmon.c
> +++ b/fs/xfs/xfs_healthmon.c
> @@ -114,8 +114,8 @@ xfs_healthmon_attach(
>  	}
>  
>  	refcount_inc(&hm->ref);
> -	rcu_assign_pointer(mp->m_healthmon, hm);
>  	hm->mount_cookie = (uintptr_t)mp->m_super;
> +	rcu_assign_pointer(mp->m_healthmon, hm);
>  	spin_unlock(&xfs_healthmon_lock);
>  
>  	return 0;
> -- 
> 2.43.0
> 
> 

  reply	other threads:[~2026-10-15 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  8:02 Binbin Deng
2026-10-15 14:38 ` Darrick J. Wong [this message]
2026-10-27 15:16 ` Christoph Hellwig

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=20261015143807.GN2705364@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=18983559317@163.com \
    --cc=cem@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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®