diff options
| author | Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> | 2024-12-13 01:21:10 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-02-17 10:04:55 +0100 |
| commit | 90778f31efdf44622065ebbe8d228284104bd26f (patch) | |
| tree | 1f2c3200213009bc8a6098e3aad96ee83f8c4127 /include | |
| parent | c021dc03bfa75f54a2d2a192358ed65aa6fc0d82 (diff) | |
| download | linux-90778f31efdf44622065ebbe8d228284104bd26f.tar.gz linux-90778f31efdf44622065ebbe8d228284104bd26f.tar.bz2 linux-90778f31efdf44622065ebbe8d228284104bd26f.zip | |
ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback
[ Upstream commit 301c26a018acb94dd537a4418cefa0f654500c6f ]
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 over-kill.
The reason why -EINVAL was ignored was it 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.
So don't use soc_pcm_ret() on .prepare callback is better idea.
Link: https://lore.kernel.org/r/87v7vptzap.wl-kuninori.morimoto.gx@renesas.com
Cc: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Link: https://patch.msgid.link/87bjxg8jju.wl-kuninori.morimoto.gx@renesas.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions