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

[Gao, K. <kev...@in...>]

1)A. yes,

I think use XML format is a good choise for user to use our FITH,
User does not need write many XML files, only edit one template can =
help
them make the trigger they want.=20
In fsml file, we should add some other attributes, (e.g. =
"interceptor").
So I think we need rediscuss the attribute. I hope we can hold the old =
name
for compatibility.

2)Need discussion.

I think locking modules is very dirty way, and make user feel not
comfortable.
But the problem is that, user always forgets to remove trigger before =
remove
interceptor, and make system oops. Is there any method to solve this
problem.
The problem worried us since the early time of FITH, I hope we can =
solve it
thoroughly.


-Kevin

-----Original Message-----
From: Wang, Stanley=20
Sent: 2003=C4=EA1=D4=C210=C8=D5 9:17
To: Zhuang, Louis; 'Rusty Lynch';
'fau...@li...'
Cc: Gao, Kevin; Wang, Frank
Subject: RE: [DISCUSSION] make decisions about ficl


A. yes
B. no

For question B, I think we could do some cleaning work when the=20
interceptor is remove to decrease the potionial issues.

-Stan

> -----Original Message-----
> From: Zhuang, Louis=20
> Sent: 2003-01-10 9:12
> To: 'Rusty Lynch'; fau...@li...
> Cc: Gao, Kevin; Wang, Frank; Wang, Stanley; Zhuang, Louis
> Subject: [DISCUSSION] make decisions about ficl
>=20
>=20
> > * 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=20
> in China. ;->
>=20
> According to ficl, we've some decisions to make.=20
> First, ficl for current FITH should still use FSML as input?
> a. yes
> b. no
> Second, ficl should lock relevant drivers/modules=20
> automatically as before?
> a. yes.
> b. no
>=20
> For second item, locking modules is a really mess which is=20
> not really relative with fault injection itself. But it can=20
> protect system from mis-operating (for example, tester always=20
> forgets remove PF trigger before unload tested-driver. This=20
> will make kernel oops because iounmap finds some MMIO page is=20
> not present.) But we can not find a clean way to lock module=20
> in user space. Shall we investigate more on this? Or shall we=20
> talk with Russell for this feature?
>=20
> Any comments?
>=20
>=20
>=20
> 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
>=20