click: Compatibility changes for kernel lock debugging #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lock correctness debugging requires that various kernel data structures
be statically allocated, instead of being allocated in dynamic
memory. One such structre is the VFS file_system_type.
Previously, proclikefs imbedded this structure inside its
proclikefs_file_system structure, which was allocated dynamically.
Instead, each client of proclikefs (actually just clickfs) now
statically allocates a file_system_type structure, and registers
this with proclikefs.
The include file semaphore.h contains a C99-style structure
initializer which is not legal in C++. This file only gets
included when spin lock debugging is enabled. Since Click does
not use sema_init(), the simple fix is to skip its compilation
by surrounding it in #ifndef __cplusplus.
The include file semaphore.h is also mangled by the fixincludes.pl
changes which are intended to only modify ktime.h. Limit the scope
of ktime-related changes to only ktime.h