Re: [Fault-injection-developer] RE: About push e100 test cases to our FITH tree

[Rusty L. <ru...@li...>]

From: "Gao, Kevin" <kev...@in...>
> Yes, put it to fith-tools is a good suggestion.
> But I want to know how will fith-tool directory existing in our project.
> The code there in is not used for much time, and overdated.
> I will try to clean up the directory.
>  
> -Kevin

I think the fact that our fith-tools code is stagnant is a direct
(and natural) result of the projects  focus on kernel level features.
As we further solidify the basic kernel interfaces, the user space
code will start to get more attention.

BTW, a well written and generally useful set of user space tools
for this type of new feature is key for the kernel space code eventually 
being accepted into Linus's tree.  We are going to have to overcome
the same *chicken-and-egg type of dilemma that kprobes is currently
suffering from.

    -rustyl

* In case the chicken-and-egg analogy is not obvious across cultural
  barriers...  it refers to the evolutionary question of which came 
  first, the chicken or the egg.  In order to have our fault injection
  capabilities (chicken) added to the kernel, we will need to have
  a significant backing of people using (egg) the features to justify
  the extra code before Linus will accept the changes.  The only
  way I see people taking advantage of fi is to have some very useful
  user space tools (fith-tools).