From: "Darrick J. Wong" <djwong@kernel.org>
To: Shigeru Yoshida <syoshida@redhat.com>
Cc: Carlos Maiolino <cem@kernel.org>,
Deepanshu Kartikey <kartikey406@gmail.com>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: fix double mutex_lock() call in xfs_ioc_health_monitor()
Date: Thu, 10 Sep 2026 07:57:20 -0700 [thread overview]
Message-ID: <20260910145720.GB6238@frogsfrogsfrogs> (raw)
In-Reply-To: <20260910132956.538828-1-syoshida@redhat.com>
On Thu, Sep 10, 2026 at 10:29:55PM +0900, Shigeru Yoshida wrote:
> Commit 4870da4f49ae ("xfs: take hm->lock in xfs_ioc_health_monitor()
> before insert") intended to protect the __xfs_healthmon_insert() call
> with hm->lock, but the second mutex operation was accidentally left as
> mutex_lock() instead of mutex_unlock(), causing self-deadlock. Change
> the second call to mutex_unlock() as originally intended.
>
> Fixes: 4870da4f49ae ("xfs: take hm->lock in xfs_ioc_health_monitor() before insert")
> Signed-off-by: Shigeru Yoshida <syoshida@redhat.com>
The original patch I reviewed unlocked hm->lock correctly, not sure how
it got corrupted by the tooling such that we need this. I think cem
fixed it already(?) but in case anyone needs it,
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 6dc3f69d6798..c3749675ef19 100644
> --- a/fs/xfs/xfs_healthmon.c
> +++ b/fs/xfs/xfs_healthmon.c
> @@ -1225,7 +1225,7 @@ xfs_ioc_health_monitor(
> running_event->domain = XFS_HEALTHMON_MOUNT;
> mutex_lock(&hm->lock);
> __xfs_healthmon_insert(hm, INSERT_HEAD, running_event);
> - mutex_lock(&hm->lock);
> + mutex_unlock(&hm->lock);
>
> /*
> * Preallocate the unmount event so that we can't fail to notify the
> --
> 2.55.0
>
>
next prev parent reply other threads:[~2026-09-10 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 13:29 Shigeru Yoshida
2026-09-10 14:57 ` Darrick J. Wong [this message]
2026-09-10 15:12 ` Carlos Maiolino
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=20260910145720.GB6238@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syoshida@redhat.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®