From: Dan Williams <dan.j.williams@intel.com>
To: Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>
Cc: <nvdimm@lists.linux.dev>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>
Subject: RE: [PATCH] ACPI: NFIT: fix a potential deadlock during NFIT teardown
Date: Wed, 25 Jan 2023 11:34:55 -0800 [thread overview]
Message-ID: <63d1845f8f86f_3a36e529441@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20230112-acpi_nfit_lockdep-v1-1-660be4dd10be@intel.com>
Vishal Verma wrote:
> Lockdep reports that acpi_nfit_shutdown() may deadlock against an
> opportune acpi_nfit_scrub(). acpi_nfit_scrub () is run from inside a
> 'work' and therefore has already acquired workqueue-internal locks. It
> also acquiires acpi_desc->init_mutex. acpi_nfit_shutdown() first
> acquires init_mutex, and was subsequently attempting to cancel any
> pending workqueue items. This reversed locking order causes a potential
> deadlock:
>
> ======================================================
> WARNING: possible circular locking dependency detected
> 6.2.0-rc3 #116 Tainted: G O N
> ------------------------------------------------------
> libndctl/1958 is trying to acquire lock:
> ffff888129b461c0 ((work_completion)(&(&acpi_desc->dwork)->work)){+.+.}-{0:0}, at: __flush_work+0x43/0x450
>
> but task is already holding lock:
> ffff888129b460e8 (&acpi_desc->init_mutex){+.+.}-{3:3}, at: acpi_nfit_shutdown+0x87/0xd0 [nfit]
>
> which lock already depends on the new lock.
>
> ...
>
> Possible unsafe locking scenario:
>
> CPU0 CPU1
> ---- ----
> lock(&acpi_desc->init_mutex);
> lock((work_completion)(&(&acpi_desc->dwork)->work));
> lock(&acpi_desc->init_mutex);
> lock((work_completion)(&(&acpi_desc->dwork)->work));
>
> *** DEADLOCK ***
>
> Since the workqueue manipulation is protected by its own internal locking,
> the cancellation of pending work doesn't need to be done under
> acpi_desc->init_mutex. Move cancel_delayed_work_sync() outside the
> init_mutex to fix the deadlock. Any work that starts after
> acpi_nfit_shutdown() drops the lock will see ARS_CANCEL, and the
> cancel_delayed_work_sync() will safely flush it out.
>
> Reported-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> ---
> drivers/acpi/nfit/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c
> index f1cc5ec6a3b6..4e48d6db05eb 100644
> --- a/drivers/acpi/nfit/core.c
> +++ b/drivers/acpi/nfit/core.c
> @@ -3297,8 +3297,8 @@ void acpi_nfit_shutdown(void *data)
>
> mutex_lock(&acpi_desc->init_mutex);
> set_bit(ARS_CANCEL, &acpi_desc->scrub_flags);
> - cancel_delayed_work_sync(&acpi_desc->dwork);
> mutex_unlock(&acpi_desc->init_mutex);
> + cancel_delayed_work_sync(&acpi_desc->dwork);
Looks good, applied.
prev parent reply other threads:[~2023-01-25 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 18:34 Vishal Verma
2023-01-25 19:34 ` Dan Williams [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=63d1845f8f86f_3a36e529441@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=vishal.l.verma@intel.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®