Completed
We implemented Kernel Patchalyzer to help analyze the patch status of embedded devices during assessments.
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Mind The Gap - The Linux Ecosystem Kernel Patch Gap
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Kernel patching is our common interest. In other words: How old is your smart TV?
- 3 Kernel patching is a complex shared responsibility.
- 4 Multiple parties are involved in kernel patching, which brings a unique set of challenges.
- 5 Ecosystem fragmentation further complicates kernel patching.
- 6 Automation can improve patching processes.
- 7 Device vendors need to make four crucial decisions early in the development process.
- 8 Kernel lifecycle and support timeframe need to be carefully planned pro-actively.
- 9 Legal requirements on support timeframe are relatively recent.
- 10 Device vendors must carefully consider the choice of Linux kernel version.
- 11 3a A best practice for embedded device vendors is using a LTS Linux kernel version.
- 12 Chipset vendors must support the chosen (LTS) kernel version and hardware requirements.
- 13 We implemented Kernel Patchalyzer to help analyze the patch status of embedded devices during assessments.
- 14 Kernel Patchalyzer helps testing for kernel patches quickly with a high confidence.
- 15 Finding available patches involves preprocessing and then searching across several kernel repositories
- 16 Automated testing involves trying to apply the patch to the analyzed kernel source code.
- 17 Duration of patch analysis is drastically reduced by optimization efforts.
- 18 Automation can be utilized to improve patching processes during development.