raspi2 config diverges from master/generic armhf
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-raspi2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
| Yakkety |
Fix Released
|
Undecided
|
Unassigned | ||
| Zesty |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
[SRU Justification]
Over the course of time, the config used for the raspi2 branch, diverged from the config used for master/generic, and that could to different behaviours for kernel that should have the same (or largely the same) set of features/options ([1] is an example of this). What follows is the manual sync between the config of master/generic and the raspi2 branch.
After this config the number of kernel modules increased from 3332 to 3547, and the size of the kernel deb package increased from 35.4MB to 37.2MB, but since many non boot essential options were factored out as modules, the kernel itself went down from 6.7MB to 5.7MB - ~1MB of code was shaved.
1: https:/
[Fix]
Manually diff the config between master/generic and raspi2, split it for built-in options and modules, apply the sets by making sure none of the boot essentials or desiderata options are turned off - finally, review the resulting config and in case of errors go back to square one.
[Testcase]
The resulting kernel was testes on rpi2/3 in ubuntu classic, and ubuntu core, in headless and video output setup, all the main components were excercised: network, video, usb, cpu freq, etc.
People should probably test it on their own setup under their workloads and report any issue found.
[Regressione potential]
With such a change there's always potential for regression, but i tried to smoke test it on as many diverse setups as possible, and i've reviewed every config change, checking that we weren't changing anything fundamental.
| description: | updated |
| description: | updated |
| Changed in linux-raspi2 (Ubuntu Xenial): | |
| status: | New → Fix Committed |
| Changed in linux-raspi2 (Ubuntu Yakkety): | |
| status: | New → Fix Committed |
| Changed in linux-raspi2 (Ubuntu Zesty): | |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in linux-raspi2 (Ubuntu Yakkety): | |
| status: | Fix Committed → Fix Released |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in linux-raspi2 (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in linux-raspi2 (Ubuntu Zesty): | |
| status: | Fix Committed → Fix Released |
| Changed in linux-raspi2 (Ubuntu): | |
| status: | New → Fix Released |
This bug was fixed in the package linux-raspi2 - 4.8.0-1042.46
---------------
linux-raspi2 (4.8.0-1042.46) yakkety; urgency=low
* linux-raspi2: 4.8.0-1042.46 -proposed tracker (LP: #1700536)
[ Ubuntu: 4.8.0-58.63 ]
* linux: 4.8.0-58.63 -proposed tracker (LP: #1700533)
* CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse stack gap into THP"
- Revert "mm: enlarge stack guard gap"
- mm: vma_adjust: remove superfluous confusing update in remove_next == 1 case
- mm: larger stack guard gap, between vmas
- mm: fix new crash in unmapped_
- Allow stack to grow up to address space limit
linux-raspi2 (4.8.0-1041.45) yakkety; urgency=low
* linux-raspi2: 4.8.0-1041.45 -proposed tracker (LP: #1699037)
* raspi2 config diverges from master/generic armhf (LP: #1693250)
- [Config] config sync wrt master/generic
- [Config] disable FB_SIMPLE
- [Config] config sync wrt master/generic =m
- remove the of_mmc_spi module
[ Ubuntu: 4.8.0-57.62 ]
* linux: 4.8.0-57.62 -proposed tracker (LP: #1699035)
* CVE-2017-1000364
- SAUCE: mm: Only expand stack if guard area is hit
* CVE-2017-7374
- fscrypt: remove broken support for detecting keyring key revocation
* CVE-2017-100363
- char: lp: fix possible integer overflow in lp_setup()
* CVE-2017-9242
- ipv6: fix out of bound writes in __ip6_append_data()
* CVE-2017-9075
- sctp: do not inherit ipv6_{mc|
* CVE-2017-9074
- ipv6: Prevent overrun when parsing v6 header options
* CVE-2017-9076
- ipv6/dccp: do not inherit ipv6_mc_list from parent
* CVE-2017-9077
- ipv6/dccp: do not inherit ipv6_mc_list from parent
* CVE-2017-8890
- dccp/tcp: do not inherit mc_list from parent
* extend-diff-ignore should use exact matches (LP: #1693504)
- [Packaging] exact extend-diff-ignore matches
* APST quirk needed for Intel NVMe (LP: #1686592)
- nvme: Quirk APST on Intel 600P/P3100 devices
* regression: the 4.8 hwe kernel does not create the
/sys/
- scsi: ses: Fix SAS device detection in enclosure
* datapath: Add missing case OVS_TUNNEL_
- openvswitch: Add missing case OVS_TUNNEL_
* connection flood to port 445 on mounting cifs volume under kernel
(LP: #1686099)
- cifs: Do not send echoes before Negotiate is complete
* Support IPMI system interface on Cavium ThunderX (LP: #1688132)
- i2c: octeon: Rename driver to prepare for split
- i2c: octeon: Split the driver into two parts
- [Config] CONFIG_
- i2c: thunderx: Add i2c driver for ThunderX SOC
- i2c: thunderx: Add SMBUS alert support
- i2c: octeon,thunderx: Move register offsets to struct
- i2c: octeon: Sort include files alphabetically
- i2c: octeon: Use booleon values for booleon variables
- i2c: octeon: thunderx: Add MAINTAINERS entry
- i2c: octeon: Fix set SCL recovery function
- i2c: octeon: Avoid sending STOP during recovery
- i2c: octeon: Fix high-level controller status che...