All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH] ASoC: hda: increment codec device refcount when it is added to the card
Date: Fri, 31 May 2019 06:52:27 -0700	[thread overview]
Message-ID: <0f75caffee97f7cec5a1bd31e9f3eb3ea1a12948.camel@linux.intel.com> (raw)
In-Reply-To: <s5hef4en4ct.wl-tiwai@suse.de>

On Fri, 2019-05-31 at 15:25 +0200, Takashi Iwai wrote:
> On Fri, 31 May 2019 15:18:03 +0200,
> Ranjani Sridharan wrote:
> > 
> > On Fri, 2019-05-31 at 08:11 +0200, Takashi Iwai wrote:
> > > On Thu, 30 May 2019 23:00:10 +0200,
> > > Pierre-Louis Bossart wrote:
> > > > 
> > > > 
> > > > 
> > > > On 5/30/19 3:18 PM, Ranjani Sridharan wrote:
> > > > > Calling snd_device_new() makes the codec devices managed by
> > > > > the
> > > > > card.
> > > > > So, when the card is removed, the refcount for the codec
> > > > > device is decremented and results in the codec device's
> > > > > kobject
> > > > > being cleaned up if the refcount is 0. But, this leads to a
> > > > > NULL
> > > > > pointer exception while attempting to remove the symlinks
> > > > > when
> > > > > the
> > > > > codec driver is released later on. Therefore, increment the
> > > > > codec
> > > > > device's refcount before adding it to the card to prevent
> > > > > this.
> > > > 
> > > > Ranjani, you should add a bit of context for the rest of the
> > > > list...
> > > > 
> > > > This patch suggest a solution to a set of sightings occurring
> > > > when
> > > > removing/adding modules in a loop, and the current analysis
> > > > points
> > > > to
> > > > a difference between the way the HDMI and HDaudio codecs are
> > > > handled.
> > > > 
> > > > https://github.com/thesofproject/linux/issues/981
> > > > https://github.com/thesofproject/linux/issues/966
> > > > https://github.com/thesofproject/linux/pull/988
> > > > 
> > > > Since it's not SOF specific it's better to get feedback
> > > > directly
> > > > from
> > > > the large ALSA community/maintainers. We probably want to focus
> > > > on
> > > > the
> > > > platform-specific/vendor-specific stuff on GitHub and use the
> > > > mailing
> > > > list for such framework-level changes.
> > > 
> > > Hm, I still wonder why this doens't happen with the HDA legacy.
> > > 
> > > What is the shortest way to trigger the bug manually without a
> > > script?
> > 
> > Hi Takashi,
> > 
> > With SOF, I can reproduce the issue if I just unload the
> > sof_pci_dev
> > module with rmmod. 
> > 
> > Basically, the remove routine for the SOF pci device, unregisters
> > the
> > machine driver and then removes the codec device. So the first step
> > of
> > unregistering the machine driver frees the card which decrements
> > the
> > refcount for the HDA codec's kobject. In the case of HDMI codec,
> > since
> > it is not managed by the card, the refcount is not decremented when
> > the
> > card is removed. 
> 
> So it's only about hdac_hdmi codec, or only about hdac_hda codec?

It is only about the hdac_hda codec. 
> 
> And why HDMI codec isn't managed by the card...?  IOW, isn't it
> dangerous -- it means the codec being always removable after bound to
> the card?
That is a good point. Probably this needs to be fixed as well. I can
include the change for that if you think it is the right thing to do.

But I was wondering if it makes sense to increment the refcount when
the device is added to the card with snd_device_new()? 
I'm not sure how it affects the other devices so didnt go down this
route.

Thanks,
Ranjani

> 
> 
> thanks,
> 
> Takashi

  reply	other threads:[~2019-05-31 13:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 20:18 [PATCH] ASoC: hda: increment codec device refcount when it is added to the card Ranjani Sridharan
2019-05-30 21:00 ` Pierre-Louis Bossart
2019-05-31  6:11   ` Takashi Iwai
2019-05-31 13:18     ` Ranjani Sridharan
2019-05-31 13:25       ` Takashi Iwai
2019-05-31 13:52         ` Ranjani Sridharan [this message]
2019-05-31 14:02           ` Takashi Iwai
2019-05-31 14:28             ` Takashi Iwai
2019-05-31 15:20               ` Ranjani Sridharan
2019-05-31 15:37                 ` Takashi Iwai
2019-05-31 15:43                   ` Ranjani Sridharan
2019-05-31 15:45                     ` Takashi Iwai

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=0f75caffee97f7cec5a1bd31e9f3eb3ea1a12948.camel@linux.intel.com \
    --to=ranjani.sridharan@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.