lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 17 Jun 2007 18:26:55 +0200
From:	Stefan Richter <>
To:	Adrian Bunk <>
CC:	Michal Piotrowski <>,
	Oleg Verych <>,
	Linus Torvalds <>,
	Andi Kleen <>,
	"Rafael J. Wysocki" <>,
	Diego Calleja <>,
	Chuck Ebbert <>,
	Linux Kernel Mailing List <>,
	Andrew Morton <>
Subject: Re: How to improve the quality of the kernel?

Adrian Bunk wrote:
>>> And we should be aware that reverting is only a workaround for the real
>>> problem which lies in our bug handling.
>> ...
> And this is something I want to emphasize again.
> How can we make any progress with the real problem and not only the 
> symptoms?

Perhaps make lists of

  - bug reports which never lead to any debug activity
    (no responsible person/team was found, or a seemingly person/team
    did not start to debug the report)

  - known regressions on release,

  - regressions that became known after release,

  - subsystems with notable backlogs of old bugs,

  - other categories?

Select typical cases from each categories, analyze what went wrong in
these cases, and try to identify practicable countermeasures.

Another approach:  Figure out areas where quality is exemplary and try
to draw conclusions for areas where quality is lacking.
Stefan Richter
-=====-=-=== -==- =---=
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists