Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Seth Forshee | ||
Bionic |
Fix Released
|
High
|
Seth Forshee |
Bug Description
SRU Justification
Impact: CONFIG_
Fix: Enable this option and set CONFIG_
Regression Potential: The kconfig help text warns of adding overhead to network tx and rx, but our analysis finds this to be negligible (see comment #6). Beyond this we are enabling a new driver which does little unless timestamping is explicitly activated, so regressions are not expected.
---
Hi folks, is there a reason we do not enable CONFIG_
CVE References
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
status: | Incomplete → Triaged |
tags: | added: kernel-key |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
tags: |
added: kernel-da-key removed: kernel-key |
Changed in linux (Ubuntu Bionic): | |
assignee: | nobody → Seth Forshee (sforshee) |
importance: | Undecided → High |
status: | New → In Progress |
description: | updated |
tags: |
added: kernel-key removed: kernel-da-key |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1785816
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.