News for hackers. Stuff that matters.
Re:Nasty Lockup Issue Still Being Investigated for Linux 3.18 by jrockway on Monday December 01, 2014 @12:36AM (#8679682)
This is a nice philosophy, but with Linux's extensive suite of automated tests (zero), I'm more surprised that it ever works at all.

The other day I was "backporting" some input patches to an older kernel version. The patches all applied cleanly. The resulting source code compiled. The feature I wanted worked. But it still scares me too much to check it in.

Re:Nasty Lockup Issue Still Being Investigated for Linux 3.18 by gioele on Monday December 01, 2014 @01:44AM (#8679815)
> Linux's extensive suite of automated tests (zero),

What about LTP [1] and Autotest [2]?

«Linux Test Project is a joint project started by SGI, OSDL and Bull developed and maintained by IBM, Cisco, Fujitsu, SUSE, Red Hat, Oracle and others. The project goal is to deliver tests to the open source community that validate the reliability, robustness, and stability of Linux.

The LTP testsuite contains a collection of tools for testing the Linux kernel and related features.»

[1] http://linux-test-project.github.io/

[2] http://autotest.github.io/

Re:Nasty Lockup Issue Still Being Investigated for Linux 3.18 by jrockway on Monday December 01, 2014 @02:19AM (#8679882)
These look pretty nice. I wish these were included with the main source tree.
Re:Nasty Lockup Issue Still Being Investigated for Linux 3.18 by cesarb on Monday December 01, 2014 @07:32AM (#8680624)
There are also a few tests within the main source tree.

Locking and RCU have built-in "torture" tests (CONFIG_LOCK_TORTURE_TEST and CONFIG_RCU_TORTURE_TEST). Take also a look at the tools/testing/ directory in the kernel source tree.