public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Nirujogi, Pratap" <pnirujog@amd.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	Pratap Nirujogi <pratap.nirujogi@amd.com>,
	andi.shyti@kernel.org, mika.westerberg@linux.intel.com,
	jsd@semihalf.com, rafael.j.wysocki@intel.com, mlimonci@amd.com,
	benjamin.chan@amd.com, bin.du@amd.com, king.li@amd.com,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] i2c: designware: amdisp: Fix null pointer dereference in runtime resume
Date: Fri, 20 Mar 2026 09:59:06 +0200	[thread overview]
Message-ID: <abz-SmE5-_OLcZb_@ashevche-desk.local> (raw)
In-Reply-To: <61dbe8a1-6578-4690-8571-6b00c1850d34@amd.com>

On Thu, Mar 19, 2026 at 05:09:55PM -0400, Nirujogi, Pratap wrote:
> On 3/9/2026 9:29 PM, Mario Limonciello wrote:
> > On 3/9/2026 5:00 PM, Pratap Nirujogi wrote:

...

> > > Fixes: 02c057ddefef ("ACPI: video: Convert the driver to a platform one")
> > 
> > Is this the right commit that introduced the race?  Did it change the
> > timing?
> > 
> > Or was the race always there and we just got lucky until that commit
> > went in?
> > 
> My apologies for mixing up this change along with other changes that were
> needed to fix the AMD ISP driver regressions in v7.0.
> 
> I investigated further and found that this issue was exposed by the below
> commit.
> 
> https://github.com/torvalds/linux/commit/38fa29b01a6a295aedb69d1bbdad70acd7d204c6

Still it might be not a culprit as at that point the device should be in power
on state.

> However, the resume‑probe race condition existed even earlier and had not
> surfaced because device initialization in resume is done only when init
> handle is valid.

That's what the initial cause, the AMD ISP driver initially relies on
the broken (racy) behaviour. So, the original patch d6263c468a761 does not
explain that bit. You need to go deeper and understand why the heck that
condition is present there.

> Here is some background and context on this change:

Exactly, the below seems that you have nailed it down.

> The amdisp i2c device requires ISP to be in power on state for probe to
> succeed. To meet this requirement, we added this device, which is a amdgpu
> MFD child to the genpd, to control isp power using runtime PM. The
> pm_runtime_get_sync() call before probe triggers a PM resume, which powers
> on the ISP and also invokes the amdisp i2c runtime resume before the probe
> completes resulting in this race condition.
> 
> To fix this issue properly, I’m considering this change. Please review and
> share your feedback on whether this makes sense.
> 
> - Call dev_pm_genpd_resume() to Power ON ISP before probe
> - Call dev_pm_genpd_suspend() to Power OFF ISP after probe
> - Call pm_runtime_enable() after probe is successful to take care of system
> suspend/resume.

I don't know the scope of dev_pm_genpd_*() usage, but the description of
the proposed change sounds sane. And definitely it's much much better than
previous attempt.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-03-20  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 22:00 [PATCH v1] i2c: designware: amdisp: Fix null pointer dereference in runtime resume Pratap Nirujogi
2026-03-10  1:29 ` Mario Limonciello
2026-03-19 21:09   ` Nirujogi, Pratap
2026-03-20  7:59     ` Andy Shevchenko [this message]
2026-03-20 15:38       ` Nirujogi, Pratap
2026-03-20 13:56     ` Mario Limonciello
2026-03-20 15:40       ` Nirujogi, Pratap
2026-03-10 11:21 ` Andy Shevchenko
2026-03-19 21:24   ` Nirujogi, Pratap

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=abz-SmE5-_OLcZb_@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=benjamin.chan@amd.com \
    --cc=bin.du@amd.com \
    --cc=jsd@semihalf.com \
    --cc=king.li@amd.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mlimonci@amd.com \
    --cc=pnirujog@amd.com \
    --cc=pratap.nirujogi@amd.com \
    --cc=rafael.j.wysocki@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