Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	 patches@opensource.cirrus.com, kunit-dev@googlegroups.com,
	 linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] firmware: cs_dsp: test_bin_error: Fix uninitialized data used as fw version
Date: Thu, 10 Apr 2025 20:16:31 +0100	[thread overview]
Message-ID: <174431259161.501489.5379480875112527733.b4-ty@kernel.org> (raw)
In-Reply-To: <20250410132129.1312541-1-rf@opensource.cirrus.com>

On Thu, 10 Apr 2025 14:21:29 +0100, Richard Fitzgerald wrote:
> Call cs_dsp_mock_xm_header_get_fw_version() to get the firmware version
> from the dummy XM header data in cs_dsp_bin_err_test_common_init().
> 
> Make the same change to cs_dsp_bin_test_common_init() and remove the
> cs_dsp_mock_xm_header_get_fw_version_from_regmap() function.
> 
> The code in cs_dsp_test_bin.c was correctly calling
> cs_dsp_mock_xm_header_get_fw_version_from_regmap() to fetch the fw version
> from a dummy header it wrote to XM registers. However in
> cs_dsp_test_bin_error.c the test doesn't stuff a dummy header into XM, it
> populates it the normal way using a wmfw file. It should have called
> cs_dsp_mock_xm_header_get_fw_version() to get the data from its blob
> buffer, but was calling cs_dsp_mock_xm_header_get_fw_version_from_regmap().
> As nothing had been written to the registers this returned the value of
> uninitialized data.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] firmware: cs_dsp: test_bin_error: Fix uninitialized data used as fw version
      commit: 285b2c74cf9982e873ef82a2cb1328d9e9406f65

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      reply	other threads:[~2025-04-10 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 13:21 [PATCH] firmware: cs_dsp: test_bin_error: Fix uninitialized data used as fw version Richard Fitzgerald
2025-04-10 19:16 ` Mark Brown [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=174431259161.501489.5379480875112527733.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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