RE: [Fault-injection-developer] [DISCUSSION] make decisions about ficl

[Lynch, R. <rus...@in...>]

> From: Zhuang, Louis [mailto:lou...@in...]
> > * In case the chicken-and-egg analogy is not obvious across cultural
> >   barriers...  it refers to the evolutionary question of which came 
> In fact, chicken-and-egg is really across cluture, at least 
> in China. ;->

Ah... I'll have to find another analogy to throw people off. :->

> 
> According to ficl, we've some decisions to make. 
> First, ficl for current FITH should still use FSML as input?
> a. yes
> b. no

I think the justification for FSML is still valid, so YES.
We could also provide some other very simple tools like
maybe a lstrigger, rmtrigger, addtrigger, etc.  (Just 
thoughts off the top of my head.)

> Second, ficl should lock relevant drivers/modules 
> automatically as before?
> a. yes.
> b. no
> 

I'm not sure I completely understand the issue, but gut
feeling is NO, and then see how bad the repercussions are
after the fact.

> For second item, locking modules is a really mess which is not really
> relative with fault injection itself. But it can protect system from
> mis-operating (for example, tester always forgets remove PF 
> trigger before
> unload tested-driver. This will make kernel oops because 
> iounmap finds some
> MMIO page is not present.) But we can not find a clean way to 
> lock module in
> user space. Shall we investigate more on this? Or shall we 
> talk with Russell
> for this feature?
> 
> Any comments?
> 
> 
> 
> Yours truly,
> Louis Zhuang
> ---------------
> Fault Injection Test Harness Project
> BK tree: http://fault-injection.bkbits.net/linux-2.5
> Home Page: http://sf.net/projects/fault-injection
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
>