From: sashiko-bot@kernel.org
To: "Sreeraj S Kurup" <sreekuttan2156239@gmail.com>
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH] ALSA: compress: Set metadata_set only after successful callback
Date: Fri, 13 Nov 2026 09:17:23 +0000 [thread overview]
Message-ID: <sashiko-outbox-212529@kernel.org> (raw)
In-Reply-To: <20261113091159.2954-1-sreekuttan2156239@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] ALSA: compress: missing Fixes trailer for commit 9727b490e543
--
commit 965fa8b5eac2d0c56694f06c6f1691a5d9ac92a3
Author: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
> ALSA: compress: Set metadata_set only after successful callback
>
> Set the metadata_set flag only when the driver's set_metadata()
> callback completes successfully.
>
> Previously, the flag was set even when the callback returned an
> error. This incorrectly indicated that metadata had been applied
> successfully, potentially causing later operations to skip metadata
> setup.
>
> Update the flag only when the callback returns zero so that its
> state accurately reflects successful metadata submission.
>
> Signed-off-by: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
[Severity: Low]
Should this commit include a Fixes tag for the commit that introduced the
unconditional assignment in snd_compr_set_metadata()?
Fixes: 9727b490e543 ("ALSA: compress: add support for gapless playback")
Also, this isn't a bug in the patch, but stream->metadata_set is only read
in snd_compr_next_track() to gate SNDRV_COMPRESS_NEXT_TRACK (returning
-EPERM when false), rather than causing later operations to skip metadata
setup.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113091159.2954-1-sreekuttan2156239@gmail.com?part=1
prev parent reply other threads:[~2026-11-13 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 9:11 [PATCH] ALSA: compress: Set metadata_set only after successful callback Sreeraj S Kurup
2026-11-13 9:17 ` sashiko-bot [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=sashiko-outbox-212529@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sreekuttan2156239@gmail.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