Skip to content

fix(tester-config): add missing CRYPTO_AES to test-runner kernel config#17

Open
deepin-ci-robot wants to merge 1 commit into
deepin-community:masterfrom
deepin-ci-robot:backport/fix-tester-config-add-missing-crypto-aes
Open

fix(tester-config): add missing CRYPTO_AES to test-runner kernel config#17
deepin-ci-robot wants to merge 1 commit into
deepin-community:masterfrom
deepin-ci-robot:backport/fix-tester-config-add-missing-crypto-aes

Conversation

@deepin-ci-robot

Copy link
Copy Markdown
Contributor

Summary

Backport upstream commit that adds missing CONFIG_CRYPTO_AES=y to the test-runner kernel config. Kernel commit 4a1507625b0 removed CRYPTO_AES from the default Bluetooth kernel config, causing Bluetooth testbots to fail silently with "Not Run" status.

Changes

  • Add debian/patches/fix-tester-config-add-missing-crypto-aes.patch
  • Modify debian/patches/series
  • Modify debian/changelog

Upstream

bluez/bluez@2470448ed

Generated-By: glm-5-turbo
Co-Authored-By: deepin-ci-robot packages@deepin.org

Kernel commit 4a1507625b0 ("Bluetooth: SMP: Use AES-CMAC library
API") removed CRYPTO_AES from the default Bluetooth kernel config.

This causes Bluetooth testbots to fail silently with "Not Run" status.
Fix by explicitly requiring CRYPTO_AES in test-runner.rst.

Note: doc/ci.config and doc/tester.config do not exist in this
downstream version, so only the test-runner.rst hunk is applied.

Changes:
  - Add debian/patches/fix-tester-config-add-missing-crypto-aes.patch
  - Modify debian/patches/series
  - Modify debian/changelog

Upstream: bluez/bluez@2470448

Generated-By: glm-5-turbo
Co-Authored-By: deepin-ci-robot <packages@deepin.org>
@github-actions

Copy link
Copy Markdown

TAG Bot

TAG: 5.85-3deepin7
EXISTED: no
DISTRIBUTION: unstable

@deepin-ci-robot

Copy link
Copy Markdown
Contributor Author

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zccrs for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant