mhocko

The primary motivation for crash-setup (created by l3team) is to make kernel crashdumps deployment and crash using as easy as possible. This has been the case for quite some time except the tool was quite l3slave centric. With a great help from tcech the tool is close to be fully usable from other machines and !.de network as well. Let's finish the last pieces. This looks like a very minor project but it will be great to have it finally!

cscope is a great tool index C/C++ sources and allow to navigate through the code. I have learned that the project is mostly dead and what is worse it uses its own database format to store the index. I would like to see some extended functionality in the tool - e.g. search whether a function A is reachable from B, filtering search results per-file, fix functions with function parameter detection (such functions are not recognized properly currently) and some others. See if the cscope specific storage can be replaced by a more generic database (sqlite?) and understand how the code flow works so that new extensions would be easier to implement.

Starting with CUPS 1.6 things have changed considerably. Clients are no longer discovering broadcasted printers anymore. Distributions (e.g. Debian) has backported the original protocol into cups-daemon package but this doesn't seem to work either on my laptop. I would like to look and try to understand what the hack is going on here. The outcome should be my understanding of the change and how to configure CUPs to behave reasonably again.

We had a quick course of Coccinelle during the last Labs conference. The tool is really great and I would like to explore possibility of checking lock invariants for particular functions. Julia was really prompt and implemented something that should help but I didn't get to it since the conference.

Project Description

Different people use different ad-hoc tools to debug Linux kernel MM (memory management) related issues. I have couple of those myself. They fall into two main categories. One set for proper data collection and the other for some high level analysis. Our customers would benefit from the former and we (L3 labs from the later). Having them in a single package sounds quite reasonable to me.