Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: "Prasad, Prasad" <venkataprasad.potturu@amd.com>
Cc: "Mukunda, Vijendar" <Vijendar.Mukunda@amd.com>,
	"Hiregoudar, Basavaraj" <Basavaraj.Hiregoudar@amd.com>,
	"Dommati, Sunil-kumar" <Sunil-kumar.Dommati@amd.com>,
	"Saba Kareem, Syed" <Syed.SabaKareem@amd.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	"open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..."
	<linux-sound@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ASoC: amd: acp: Fix incorrect retrival of acp_chip_info
Date: Wed, 10 Sep 2025 15:53:29 +0200	[thread overview]
Message-ID: <d2f8e45e-c289-4649-b764-8ded15f0bb16@intel.com> (raw)
In-Reply-To: <PH7PR12MB5951638E3C707F3B97B46567E90EA@PH7PR12MB5951.namprd12.prod.outlook.com>

On 2025-09-10 3:39 PM, Prasad, Prasad wrote:
> 
> On 9/10/2025 2:41 PM, Cezary Rojewski wrote:
>> On 2025-09-09 8:19 AM, Venkata Prasad Potturu wrote:
>>> Use dev_get_drvdata(dev->parent) instead of dev_get_platdata(dev)
>>> to correctly get acp_chip_info members in acp I2S driver.
>>> This resolves issues where some members were zero due to incorrect
>>> data access.
>>
>> Hi,
>>
>> 'some members were zero' meaning null-ptr-deref? If so, please reword
>> to make it more explicit.
> It's not a null-ptr-deref, members were not updated properly, will
> rephrase the commit description
>>
>> Given the history of this file, mainly Commit 6d9b64156d84 ("ASoC:
>> amd: acp: Fix NULL pointer deref in acp_i2s_set_tdm_slot") it's kind
>> of surprising that the issue is addressed in staggered fashion. Why
>> was set_tdm_slot() fixed separately?
> This fix was missed earlier at the time of this commit 6d9b64156d84.

Let's mention that in the commit message then. It's clear now that the 
earlier fix is insufficient and null-ptr-derefs may still occur.

>>
>>> Fixes: e3933683b25e ("ASoC: amd: acp: Remove redundant acp_dev_data
>>> structure")
>>>
>>> Signed-off-by: Venkata Prasad Potturu <venkataprasad.potturu@amd.com>
>>
>> No newline between the tags, please.
> Okay, will send v2 patch.

  reply	other threads:[~2025-09-10 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  6:19 [PATCH] ASoC: amd: acp: Fix incorrect retrival of acp_chip_info Venkata Prasad Potturu
2025-09-10  9:11 ` Cezary Rojewski
2025-09-10 13:39   ` Prasad, Prasad
2025-09-10 13:53     ` Cezary Rojewski [this message]
2025-09-16 12:08 ` Mark Brown

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=d2f8e45e-c289-4649-b764-8ded15f0bb16@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=Syed.SabaKareem@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peterz@infradead.org \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=venkataprasad.potturu@amd.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