From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: clemens@ladisch.de, perex@perex.cz, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, darrena092@gmail.com,
weiyj_lk@163.com
Subject: Re: [PATCH 1/3] bebob: Fix a missing to unlock mutex in error handling case
Date: Tue, 22 Jul 2014 16:26:50 +0200 [thread overview]
Message-ID: <s5hmwc1lb9x.wl%tiwai@suse.de> (raw)
In-Reply-To: <1406038263-18558-1-git-send-email-o-takashi@sakamocchi.jp>
At Tue, 22 Jul 2014 23:11:03 +0900,
Takashi Sakamoto wrote:
>
> In error handling case, special_clk_ctl_put() returns without unlock_mutex(),
> therefore the mutex is still locked. This commit moves mutex_lock() after
> the error handling case.
>
> This commit is my solution for this post.
>
> [PATCH -next] ALSA: bebob: Fix missing unlock on error in special_clk_ctl_put()
> https://lkml.org/lkml/2014/7/20/12
>
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Thanks, applied all three patches now.
BTW, at the next time, put "v2" or such in the subject line so that
people can distinguish the new patch series from the previous ones.
You can use --subject-prefix option for git-format-patch or else.
Preferably, write the changes since the previous revision, too
(usually below the --- line, so that it's not merged into the git
changelog; some people like to have them in the final commit,
though.)
Last but not least, don't forget to put a proper subject prefix.
For ALSA codes, we put "ALSA:" prefix in the subject. Study git
changelogs.
Takashi
> ---
> sound/firewire/bebob/bebob_maudio.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/firewire/bebob/bebob_maudio.c b/sound/firewire/bebob/bebob_maudio.c
> index 6af50eb..fc470c6 100644
> --- a/sound/firewire/bebob/bebob_maudio.c
> +++ b/sound/firewire/bebob/bebob_maudio.c
> @@ -379,12 +379,12 @@ static int special_clk_ctl_put(struct snd_kcontrol *kctl,
> struct special_params *params = bebob->maudio_special_quirk;
> int err, id;
>
> - mutex_lock(&bebob->mutex);
> -
> id = uval->value.enumerated.item[0];
> if (id >= ARRAY_SIZE(special_clk_labels))
> return 0;
>
> + mutex_lock(&bebob->mutex);
> +
> err = avc_maudio_set_special_clk(bebob, id,
> params->dig_in_fmt,
> params->dig_out_fmt,
> --
> 1.9.1
>
prev parent reply other threads:[~2014-07-22 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 4:50 [PATCH -next] ALSA: bebob: Fix missing unlock on error in special_clk_ctl_put() weiyj_lk
2014-07-20 7:51 ` Takashi Sakamoto
2014-07-22 14:11 ` [PATCH 1/3] bebob: Fix a missing to unlock mutex in error handling case Takashi Sakamoto
2014-07-22 14:26 ` Takashi Iwai [this message]
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=s5hmwc1lb9x.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=darrena092@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--cc=weiyj_lk@163.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
all inboxes | Powered by JetHome®