From: Hans de Goede <hdegoede@redhat.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH] ASoC: soc-pcm: don't ignore -EINVAL on soc_pcm_ret()
Date: Thu, 12 Dec 2024 10:43:28 +0100 [thread overview]
Message-ID: <8ba4dbc0-323e-47cf-9d74-88495f4c40a2@redhat.com> (raw)
In-Reply-To: <87v7vptzap.wl-kuninori.morimoto.gx@renesas.com>
Hi,
On 12-Dec-24 3:23 AM, Kuninori Morimoto wrote:
> commit 1f5664351410 ("ASoC: lower "no backend DAIs enabled for ... Port"
> log severity") ignores -EINVAL error message on common soc_pcm_ret().
> It is used from many functions, ignoring -EINVAL is not good idea.
>
> The reason why -EINVAL was ignored is only for ignoring
> dpcm_fe_dai_prepare() error flood.
> It should be handled at dpcm_fe_dai_prepare() side, not soc_pcm_ret()
> side.
-EINVAL really should only be used upon invalid parameters coming from
userspace and in that case we don't want to log an error since we do
not want to give userspace a way to do a denial-of-service attack
on the syslog / diskspace.
I'm not convinced that this change is a good idea, but I also
have no strong objections.
There also is a bug in this patch which needs to be fixed before this
can be accepted, see my inline comment below.
> Cc: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> sound/soc/soc-pcm.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/sound/soc/soc-pcm.c b/sound/soc/soc-pcm.c
> index 1150455619aa4..7ea580f0a6f7f 100644
> --- a/sound/soc/soc-pcm.c
> +++ b/sound/soc/soc-pcm.c
> @@ -38,7 +38,6 @@ static inline int _soc_pcm_ret(struct snd_soc_pcm_runtime *rtd,
> switch (ret) {
> case -EPROBE_DEFER:
> case -ENOTSUPP:
> - case -EINVAL:
> break;
> default:
> dev_err(rtd->dev,
> @@ -2560,8 +2559,8 @@ static int dpcm_fe_dai_prepare(struct snd_pcm_substream *substream)
> fe->dai_link->name);
> dev_dbg(fe->dev, "ASoC: no backend DAIs enabled for %s\n",
> fe->dai_link->name);
> - ret = -EINVAL;
> - goto out;
> + /* don't use soc_pcm_ret() to lower error log severity */
> + return -EINVAL;
You cannot just do a return here, you are now missing these 2 lines from
the "goto out" path:
dpcm_set_fe_update_state(fe, stream, SND_SOC_DPCM_UPDATE_NO);
snd_soc_dpcm_mutex_unlock(fe);
> }
>
> ret = dpcm_be_dai_prepare(fe, stream);
Regards,
Hans
next prev parent reply other threads:[~2024-12-12 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 2:23 [PATCH] ASoC: soc-pcm: don't ignore -EINVAL on soc_pcm_ret() Kuninori Morimoto
2024-12-12 9:43 ` Hans de Goede [this message]
2024-12-13 0:25 ` Kuninori Morimoto
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=8ba4dbc0-323e-47cf-9d74-88495f4c40a2@redhat.com \
--to=hdegoede@redhat.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sound@vger.kernel.org \
/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