Disable Bluetooth in cloud kernels

Bug #1840488 reported by Tyler Hicks on 2019-08-16
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-aws (Ubuntu)
Status tracked in Eoan
Xenial
Undecided
Unassigned
Bionic
Undecided
Unassigned
Disco
Undecided
Unassigned
Eoan
High
Unassigned
linux-gcp (Ubuntu)
Status tracked in Eoan
Xenial
High
Unassigned
Bionic
High
Unassigned
Disco
High
Unassigned
Eoan
High
Unassigned
linux-gke-4.15 (Ubuntu)
Status tracked in Eoan
Xenial
Undecided
Unassigned
Bionic
High
Unassigned
Disco
Undecided
Unassigned
Eoan
Undecided
Unassigned
linux-gke-5.0 (Ubuntu)
Status tracked in Eoan
Xenial
Undecided
Unassigned
Bionic
High
Unassigned
Disco
Undecided
Unassigned
Eoan
Undecided
Unassigned
linux-oracle (Ubuntu)
Status tracked in Eoan
Xenial
High
Unassigned
Bionic
High
Unassigned
Disco
High
Unassigned
Eoan
High
Unassigned

Bug Description

[Impact]

Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes.

The cloud kernels known to have bluetooth enabled include:

* [B/D/E] linux-aws (arm64 only)
* [X/B/D/E] linux-gcp
* [B] linux-gke-4.15
* [B] linux-gke-5.0
* [X/B/D/E] linux-oracle

[Test Case]

1. Install patched kernel and reboot into it
2. Ensure that the following command does NOT display any output:
   $ grep CONFIG_BT=[my] /boot/config-$(uname -r)

[Regression Potential]

There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely.

Tyler Hicks (tyhicks) on 2019-08-16
Changed in linux-aws (Ubuntu Disco):
status: New → Triaged
Changed in linux-aws (Ubuntu Bionic):
status: New → Triaged
description: updated
Changed in linux-aws (Ubuntu Xenial):
status: New → Invalid
Tyler Hicks (tyhicks) on 2019-08-16
Changed in linux-gke-4.15 (Ubuntu Xenial):
status: New → Invalid
Changed in linux-gke-4.15 (Ubuntu Disco):
status: New → Invalid
Changed in linux-gke-4.15 (Ubuntu Eoan):
status: New → Invalid
Changed in linux-gke-5.0 (Ubuntu Xenial):
status: New → Invalid
Changed in linux-gke-5.0 (Ubuntu Disco):
status: New → Invalid
Changed in linux-gke-5.0 (Ubuntu Eoan):
status: New → Invalid
Changed in linux-gke-4.15 (Ubuntu Bionic):
status: New → Triaged
Changed in linux-gke-5.0 (Ubuntu Bionic):
importance: Undecided → High
status: New → Triaged
Changed in linux-gke-4.15 (Ubuntu Bionic):
importance: Undecided → High
Changed in linux-gcp (Ubuntu Xenial):
status: New → Triaged
importance: Undecided → High
Changed in linux-gcp (Ubuntu Bionic):
importance: Undecided → High
status: New → Triaged
Changed in linux-gcp (Ubuntu Disco):
importance: Undecided → High
status: New → Triaged
Changed in linux-gcp (Ubuntu Eoan):
importance: Undecided → High
status: New → Triaged
Changed in linux-oracle (Ubuntu Xenial):
importance: Undecided → High
status: New → Triaged
Changed in linux-oracle (Ubuntu Bionic):
importance: Undecided → High
status: New → Triaged
Changed in linux-oracle (Ubuntu Disco):
importance: Undecided → High
status: New → Triaged
Changed in linux-oracle (Ubuntu Eoan):
importance: Undecided → High
status: New → Triaged
Tyler Hicks (tyhicks) on 2019-08-16
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers