public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Maarten Lankhorst <dev@lankhorst.se>
Cc: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
	linux-kernel@vger.kernel.org, intel-xe@lists.freedesktop.org,
	Mukesh Ojha <quic_mojha@quicinc.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	stable@vger.kernel.org, Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH] devcoredump: Fix circular locking dependency with devcd->mutex.
Date: Mon, 6 Oct 2025 11:24:16 +0200	[thread overview]
Message-ID: <2025100655-prankish-parking-9059@gregkh> (raw)
In-Reply-To: <977e15c2-ad91-45c4-be99-0390ae7f8315@lankhorst.se>

On Mon, Oct 06, 2025 at 11:11:01AM +0200, Maarten Lankhorst wrote:
> >> @@ -401,13 +424,20 @@ void dev_coredumpm_timeout(struct device *dev, struct module *owner,
> >>  
> >>  	dev_set_uevent_suppress(&devcd->devcd_dev, false);
> >>  	kobject_uevent(&devcd->devcd_dev.kobj, KOBJ_ADD);
> >> -	INIT_DELAYED_WORK(&devcd->del_wk, devcd_del);
> >> -	schedule_delayed_work(&devcd->del_wk, timeout);
> >> +
> >> +	/*
> >> +	 * Safe to run devcd_del() now that we are done with devcd_dev.
> >> +	 * Alternatively we could have taken a ref on devcd_dev before
> >> +	 * dropping the lock.
> >> +	 */
> >> +	devcd->init_completed = true;
> >>  	mutex_unlock(&devcd->mutex);
> >>  	return;
> >>   put_device:
> >> -	put_device(&devcd->devcd_dev);
> >>  	mutex_unlock(&devcd->mutex);
> >> +	cancel_delayed_work_sync(&devcd->del_wk);
> >> +	put_device(&devcd->devcd_dev);
> >> +
> > 
> > Acked-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> 
> Thanks, through what tree can this be merged?

I can look into doing that after -rc1 is out.

thanks,

greg k-h

  reply	other threads:[~2025-10-06  9:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 14:24 [PATCH] devcoredump: Fix circular locking dependency with devcd->mutex Maarten Lankhorst
2025-10-03 13:29 ` Maarten Lankhorst
2025-10-03 18:00 ` Mukesh Ojha
2025-10-06  9:11   ` Maarten Lankhorst
2025-10-06  9:24     ` Greg Kroah-Hartman [this message]
2025-10-24  8:12 ` Johannes Berg
2025-10-24  8:37   ` Maarten Lankhorst
2025-10-24  8:39     ` Johannes Berg
2025-10-24 10:27       ` Maarten Lankhorst

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=2025100655-prankish-parking-9059@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dakr@kernel.org \
    --cc=dev@lankhorst.se \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=mukesh.ojha@oss.qualcomm.com \
    --cc=quic_mojha@quicinc.com \
    --cc=rafael@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