From: Jon Hunter <jonathanh@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Mark Brown <broonie@kernel.org>,
Gui-Dong Han <hanguidong02@gmail.com>,
gregkh@linuxfoundation.org, rafael@kernel.org,
linux-kernel@vger.kernel.org, baijiaju1990@gmail.com,
Qiu-ji Chen <chenqiuji666@gmail.com>,
Aishwarya.TCV@arm.com,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v5] driver core: enforce device_lock for driver_match_device()
Date: Thu, 22 Jan 2026 17:28:12 +0000 [thread overview]
Message-ID: <f10007af-3629-4769-b89c-bbf4aa013bf3@nvidia.com> (raw)
In-Reply-To: <DFULF717AOGG.GY8B9ET26KND@kernel.org>
Hi Danilo,
On 21/01/2026 21:42, Danilo Krummrich wrote:
> On Wed Jan 21, 2026 at 9:00 PM CET, Jon Hunter wrote:
>> It is odd because it only appears to impact the Tegra194 Jetson Xavier
>> NX board (tegra194-p3509-0000+p3668-0000.dts).
>>
>> It appears to boot enough so the test can SSH into the device, but the
>> kernel log does not show the us getting to the console prompt. It also
>> appears that a lot of drivers are not bound as expected. I would need to
>> check if those are all modules or not.
>
> The other reports were fixed by [1], but the issue in arm-smmu-qcom shouldn't be
> related in this case.
>
> I quickyl checked all drivers with "tegra194" in their compatible string, but
> didn't see anything odd.
>
> Can you please try to enable CONFIG_LOCKDEP, CONFIG_PROVE_LOCKING,
> CONFIG_DEBUG_MUTEXES and see if you get a lockdep splat using the following
> diff?
>
> (You will see a lockdep warning in faux_bus_init(), it's harmless and can be
> ignored.)
Thanks. I do the lockdep warning in faux_bus_init() but that's the only
one. I have verified that all these CONFIGs are correctly enabled in the
build. The device boots fine with the below diff, but I am guessing that
that is expected?
Any other thoughts?
Thanks
Jon
> [1]
https://lore.kernel.org/driver-core/20260121141215.29658-1-dakr@kernel.org/
>
> diff --git a/drivers/base/base.h b/drivers/base/base.h
> index 677320881af1..4741412d7e46 100644
> --- a/drivers/base/base.h
> +++ b/drivers/base/base.h
> @@ -190,8 +190,13 @@ static inline int driver_match_device(const struct device_driver *drv,
> static inline int driver_match_device_locked(const struct device_driver *drv,
> struct device *dev)
> {
> - guard(device)(dev);
> - return driver_match_device(drv, dev);
> + int ret;
> +
> + mutex_acquire(&dev->mutex.dep_map, 0, 0, _THIS_IP_);
> + ret = driver_match_device(drv, dev);
> + mutex_release(&dev->mutex.dep_map, _THIS_IP_);
> +
> + return ret;
> }
>
> static inline void dev_sync_state(struct device *dev)
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index 40de2f51a1b1..56c62b3016aa 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -2557,6 +2557,8 @@ static void device_release(struct kobject *kobj)
>
> kfree(dev->dma_range_map);
>
> + lockdep_unregister_key(&dev->lock_key);
> +
> if (dev->release)
> dev->release(dev);
> else if (dev->type && dev->type->release)
> @@ -3159,7 +3161,9 @@ void device_initialize(struct device *dev)
> kobject_init(&dev->kobj, &device_ktype);
> INIT_LIST_HEAD(&dev->dma_pools);
> mutex_init(&dev->mutex);
> - lockdep_set_novalidate_class(&dev->mutex);
> + //lockdep_set_novalidate_class(&dev->mutex);
> + lockdep_register_key(&dev->lock_key);
> + lockdep_set_class(&dev->mutex, &dev->lock_key);
> spin_lock_init(&dev->devres_lock);
> INIT_LIST_HEAD(&dev->devres_head);
> device_pm_init(dev);
> diff --git a/include/linux/device.h b/include/linux/device.h
> index 0be95294b6e6..dc898a420bc2 100644
> --- a/include/linux/device.h
> +++ b/include/linux/device.h
> @@ -579,6 +579,7 @@ struct device {
> struct mutex mutex; /* mutex to synchronize calls to
> * its driver.
> */
> + struct lock_class_key lock_key;
>
> struct dev_links_info links;
> struct dev_pm_info power;
>
--
nvpublic
next prev parent reply other threads:[~2026-01-22 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260113162843.12712-1-hanguidong02@gmail.com>
[not found] ` <7ae38e31-ef31-43ad-9106-7c76ea0e8596@sirena.org.uk>
[not found] ` <CGME20260120152328eucas1p1024a7488ae10b8b7f2fcb74baee24c75@eucas1p1.samsung.com>
[not found] ` <ef37ed64-24ad-4b82-bc6c-d3bc72aaf232@samsung.com>
2026-01-21 20:00 ` [PATCH v5] driver core: enforce device_lock for driver_match_device() Jon Hunter
2026-01-21 21:42 ` Danilo Krummrich
2026-01-22 17:28 ` Jon Hunter [this message]
2026-01-22 17:55 ` Gui-Dong Han
2026-01-22 18:12 ` Danilo Krummrich
2026-01-22 18:58 ` Jon Hunter
2026-01-22 19:35 ` Danilo Krummrich
2026-01-23 13:57 ` Jon Hunter
2026-01-23 14:09 ` Danilo Krummrich
2026-01-23 14:29 ` Jon Hunter
2026-01-23 16:54 ` Danilo Krummrich
2026-01-23 18:53 ` Gui-Dong Han
2026-01-23 19:07 ` Danilo Krummrich
2026-01-27 14:58 ` Jon Hunter
2026-01-27 15:18 ` Danilo Krummrich
2026-01-27 14:53 ` Jon Hunter
2026-01-27 15:05 ` Gui-Dong Han
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=f10007af-3629-4769-b89c-bbf4aa013bf3@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=Aishwarya.TCV@arm.com \
--cc=baijiaju1990@gmail.com \
--cc=broonie@kernel.org \
--cc=chenqiuji666@gmail.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hanguidong02@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rafael@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