Language Selection

English French German Italian Portuguese Spanish

Kernel space: Bisection divides users and developers

Filed under
Linux

The last couple of years have seen a renewed push within the kernel community to avoid regressions. When a patch is found to have broken something that used to work, a fix must be merged or the offending patch will be removed from the kernel. It's a straightforward and logical idea, but there's one little problem: when a kernel series includes over 12,000 changesets (as 2.6.25 does), how does one find the patch which caused the problem? Sometimes it will be obvious, but, for other problems, there are literally thousands of patches which could be the source of the regression. Digging through all of those patches in search of a bug can be a needle-in-the-haystack sort of proposition.

One of the many nice tools offered by the git source code management system is called "bisect." The bisect feature helps the user perform a binary search through a range of patches until the one containing the bug is found. All that is needed is to specify the most recent kernel which is known to work (2.6.24, say), and the oldest kernel which is broken (2.6.25-rc9, perhaps), and the bisect feature will check out a version of the kernel at the midpoint between those two. Finding that midpoint is non-trivial, since, in git, the stream of patches is not a simple line. But that's the sort of task we keep computers around for. Once the midpoint kernel has been generated, the person chasing the bug can build and test it, then tell git whether it exhibits the bug or not. A kernel at the new midpoint will be produced, and the process continues. With bisect, the problematic patch can be found in a maximum of a dozen or so compile-boot-test cycles.

Bisect is not a perfect tool.




More in Tux Machines

Android Leftovers

This Is How the New Linux Mint 18 Cinnamon Theme Looks Like

Linux Mint project leader and maintainer Clement Lefebvre dropped some exciting news today about what users should expect from the upcoming Linux Mint 18 "Sarah" operating system. Read more

The May 2016 Issue of the PCLinuxOS Magazine

The PCLinuxOS Magazine staff is pleased to announce the release of the May 2016 issue. With the exception of a brief period in 2009, The PCLinuxOS Magazine has been published on a monthly basis since September, 2006. The PCLinuxOS Magazine is a product of the PCLinuxOS community, published by volunteers from the community. The magazine is lead by Paul Arnote, Chief Editor, and Assistant Editor Meemaw. The PCLinuxOS Magazine is released under the Creative Commons Attribution- NonCommercial-Share-Alike 3.0 Unported license, and some rights are reserved. In the May 2016 issue: * Netflix On PCLinuxOS: 18 Months Later * TubiTV: A Free Streaming Alternative * ms_meme's Nook: PCLinuxOS Is The Top * PCLinuxOS Family Member Spotlight: jlane01 * GIMP Tutorial: Make A Folded Map * Game Zone: Zombasite * PCLinuxOS Recipe Corner * Tip Top Tips: Update Your BIOS The Easy Way * PCLinuxOS Puzzled Partitions * And much more inside! This month’s magazine cover image was designed by Paul Arnote. Download the PDF (8.1 MB) http://pclosmag.com/download.php?f=2016-05.pdf Download the EPUB Version (4.9 MB) http://pclosmag.com/download.php?f=201605epub.epub Download the MOBI Version (9.0 MB) http://pclosmag.com/download.php?f=201605mobi.mobi Visit the HTML Version http://pclosmag.com/html/enter.html

A step ahead on Drupal 8 with easy accessibility design

The biggest mistake is bigger than Drupal: They don't consider it at all. This isn't a platform thing, it's a problem that is endemic to the web. Big companies get dragged into accessibility via legal threats. Small companies don't even think about it. Just the act of raising accessibility as an issue, and asking your team to keep it in mind throughout the design and development process is a big deal. You have to start somewhere. Read more