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

Linux Devices

Open Source Software A Core Competency For Effective Tech M&A

Imagine your company just acquired its competitor for $100 million. Now imagine the company’s most important asset – its proprietary software – is subject to third-party license conditions that require the proprietary software to be distributed free of charge or in source code form. Or, imagine these license conditions are discovered late in the diligence process, and the cost to replace the offending third-party software will costs tens of thousands of dollars and take months to remediate. Both scenarios exemplify the acute, distinct and often overlooked risks inherent to the commercial use of open source software. An effective tech M&A attorney must appreciate these risks and be prepared to take the steps necessary to mitigate or eliminate them. Over the past decade, open source software has become a mainstay in the technology community. Since its beginnings, open source software has always been viewed as a way to save money and jumpstart development projects, but it is increasingly being looked to for its quality solutions and operational advantages. Today, only a fraction of technology companies do not use open source software in any way. For most of the rest, it is mission critical. Read more

AMD Graphics

SUSE Leftovers

  • Git, Kernels, LightDM, More update in Tumbleweed
    Topping the list of updates for snapshot 20161129 was the update to Light Display Manager 1.21.1, which added an Application Programming Interface (API) version to the greeter-daemon protocol for future enhancements. Other updates in the snapshot include openVPN, which added a recommended utility for network and traffic protocols, and subpackages for systemd relevant for 32-bit users. Desktop manager xfdesktop updated to version 4.12.3 and introduced rotating wallpaper images if the images contain rotation information. The programming language vala, which aims to bring modern programming language features to GNOME developers without imposing any additional runtime requirements, updated in the 20161129 and 20161201 snapshots.
  • openSUSE Leap 42.1 upgrade to Leap 42.2
  • openSUSE Tumbleweed – Review of the Week 2016/49
    I’m sure nobody doubted it, but Tumbleweed is back on the roll! And in fact, we did the impossible and released 8 snapshots in a week. This review will cover {1201..1208}.