From: Alex Elder <elder@linaro.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: greybus-dev@lists.linaro.org, Alex Elder <elder@kernel.org>,
Johan Hovold <johan@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [greybus-dev] [PATCH] staging: greybus: Add missing rwsem around snd_ctl_remove() calls
Date: Wed, 17 Nov 2021 15:55:06 -0600 [thread overview]
Message-ID: <b0d2b643-214a-07c5-96b7-4845c54cba72@linaro.org> (raw)
In-Reply-To: <s5h5ysqlcm8.wl-tiwai@suse.de>
On 11/17/21 3:02 PM, Takashi Iwai wrote:
> On Wed, 17 Nov 2021 20:56:14 +0100,
> Alex Elder wrote:
>>
>> On 11/16/21 1:20 AM, Takashi Iwai wrote:
>>> snd_ctl_remove() has to be called with card->controls_rwsem held (when
>>> called after the card instantiation). This patch adds the missing
>>> rwsem calls around it.
>>
>> I see the comment above snd_ctl_remove() that says you must hold
>> the write lock. And given that, this seems correct to me.
>>
>> I understand why you want to take the lock just once, rather
>> than each time snd_ctl_remove() is called.
>>
>> However I believe the acquisition and release of the lock
>> belongs inside gbaudio_remove_controls(), not in its caller.
>>
>> If you disagree, can you please explain why?
>
> In general if the function returns an error and has a loop inside,
> taking a lock in the caller side avoids the forgotten unlock.
But taking the lock in the called function makes the
caller not need to take the lock (which would be even
more valuable if there were more than one caller).
I prefer having the lock acquisition in the called
function. Please send version 2, as I suggested.
-Alex
> Takashi
>
>
>> Otherwise, will you please submit version two, taking the
>> lock inside gbaudio_remove_controls()?
>>
>> Thanks.
>>
>> -Alex
>>
>>> Fixes: 510e340efe0c ("staging: greybus: audio: Add helper APIs for dynamic audio modules")
>>> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>>> ---
>>> drivers/staging/greybus/audio_helper.c | 8 ++++++--
>>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/staging/greybus/audio_helper.c b/drivers/staging/greybus/audio_helper.c
>>> index 1ed4772d2771..843760675876 100644
>>> --- a/drivers/staging/greybus/audio_helper.c
>>> +++ b/drivers/staging/greybus/audio_helper.c
>>> @@ -192,7 +192,11 @@ int gbaudio_remove_component_controls(struct snd_soc_component *component,
>>> unsigned int num_controls)
>>> {
>>> struct snd_card *card = component->card->snd_card;
>>> + int err;
>>> - return gbaudio_remove_controls(card, component->dev, controls,
>>> - num_controls, component->name_prefix);
>>> + down_write(&card->controls_rwsem);
>>> + err = gbaudio_remove_controls(card, component->dev, controls,
>>> + num_controls, component->name_prefix);
>>> + up_write(&card->controls_rwsem);
>>> + return err;
>>> }
>>>
>>
next prev parent reply other threads:[~2021-11-17 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 7:20 Takashi Iwai
2021-11-17 19:56 ` [greybus-dev] " Alex Elder
2021-11-17 21:02 ` Takashi Iwai
2021-11-17 21:55 ` Alex Elder [this message]
2021-11-18 3:32 ` Vaibhav Agarwal
2021-11-18 6:55 ` 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=b0d2b643-214a-07c5-96b7-4845c54cba72@linaro.org \
--to=elder@linaro.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®