fault-injection-developer Mailing List for Fault Injection Test Harness (Page 4)
Status: Alpha
Brought to you by:
rustyl
Menu
▾
▴
fault-injection-developer — Developer discussions about creating a fault injection test harness.
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(13) |
Sep
(2) |
Oct
(49) |
Nov
(69) |
Dec
(70) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(64) |
Feb
(41) |
Mar
(25) |
Apr
(18) |
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2016 |
Jan
(2) |
Feb
(5) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
|
From: Rusty L. <ru...@li...> - 2003-02-19 16:22:18
|
Kevin,
Could you publish a test plan with detailed test procedures for
recreating your e100 test cases. For the purposes of the fault
injection project, it is actually more valuable to see a practical
example of how to utilize the fault injection features to perform useful
device driver testing then it is to publish the results of testing. =20
(Don't get me wrong, test results are a good thing, especially if you
find a reproducible bug.)
--rustyl
On Wed, 2003-02-19 at 01:35, Wang, Stanley wrote:
> =20
>=20
> -----Original Message-----
> From: Gao, Kevin=20
> Sent: 2003-02-19 17:01
> To: Zhuang, Louis; Wang, Frank; Wang, Stanley
> Subject: e100 frame reception test result draft.
>=20
>=20
> E100 frame reception test has been done, the result draft is as follow:
>=20
> any comment? :)
>=20
> =20
>=20
> -Kevin
>=20
> =20
>=20
> 1. Set =E2=80=98S=E2=80=99 bit of RFD which is under received when dr=
iver reads the
> SCB status register. Driver always send a RU_START command.=20
>=20
> =20
>=20
> OK. The e100 driver checks the hardware status and reacts properly :)
>=20
> =20
>=20
> 2. Set =E2=80=98S=E2=80=99 bit of RFD which has been received when dr=
iver reads the
> SCB status register. Driver ignores the operation.=20
>=20
> =20
>=20
> OK. The 'S' bit is set by driver and read by hardware. Hence the driver
> doesn't care it.=20
>=20
> <?xml:namespace prefix =3D o ns =3D "urn:schemas-microsoft-com:office:off=
ice" />
>=20
>=20
> 3. Set both =E2=80=98C=E2=80=99 and =E2=80=98OK=E2=80=99 bit of RFD t=
o zero when driver reads the
> SCB status register, the network cannot start, and driver will hanged, a
> timeout will throw out.=20
>=20
> If the 'C' bit equals zero, the driver will treat this rfd as an incomple=
te
> packet and just wait untile 'C' equals one.=20
>=20
> =20
>=20
> 4. Set =E2=80=98C=E2=80=99 bit of RFD to 0, and set =E2=80=98OK=E2=80=
=99 bit of RFD to 1 when driver
> reads the SCB status register, the result is the same as process 2.=20
>=20
> =20
>=20
> process 2 or 3 ?
>=20
> =20
>=20
> =20
>=20
> 5. Set =E2=80=98C=E2=80=99 bit of RFD to 1, and set =E2=80=98OK=E2=80=
=99 bit of RFD to 0 when driver
> reads the SCB status register, the result is the same as process 2.=20
>=20
> =20
>=20
> process 2 or 3 ?=20
>=20
> =20
>=20
> 6. Set =E2=80=98CRC=E2=80=99 bit of RFD to 1 when driver reads the SC=
B status
> register, the driver ignores this operation.=20
>=20
> =20
>=20
> The driver should check this bit.
>=20
> =20
>=20
> =20
>=20
> 7. Set =E2=80=98Alignment error=E2=80=99 bit of RFD to 1 when driver =
reads the SCB
> status register, the driver ignores this operation.=20
>=20
> =20
>=20
> The driver should check this bit.=20
>=20
> =20
>=20
> 8. Set =E2=80=98Run out of buffer=E2=80=99 bit of RFD to 1 when drive=
r reads the SCB
> status register, the driver ignores this operation.
>=20
> =20
>=20
> The driver should check this bit.
>=20
> 9. Set =E2=80=98Frame too short=E2=80=99 bit of RFD to 1 when driver =
reads the SCB
> status register, the driver ignores this operation.
>=20
> The driver should check this bit.
> =20
> =20
> =20
>=20
|
|
From: Mark H. <ma...@os...> - 2003-02-19 16:17:55
|
On Tue, 2003-02-18 at 16:33, Louis Zhuang wrote: > On Wed, 2003-02-19 at 00:49, Mark Haverkamp wrote: > > OK, I assume that what you want showed up in dmesg. If this isn't the > > right data let me know where to look. > > > > > > > > FI_TEST: 309 jiffies = 90033991 > > #310 fi_test : COMMAND_IO_READ > > #311 fi_test : Expect read 0X5A* from parellel port register! > > > > #312 fi_test : 0XFF was read from parellel port register! > Oh... it is the evil. fi_test assume your parellel is on 0x378. your can > change the port address in fi_test.c:36 > > - Louis Thanks. I checked my BIOS setup and the parallel port was disabled. I enabled it and tried the echo command and this time it looks like it worked. Feb 19 08:21:02 markh2 kernel: FI_TEST: 77 jiffies = 2189976 Feb 19 08:21:02 markh2 kernel: #78 fi_test : COMMAND_IO_READ Feb 19 08:21:02 markh2 kernel: #79 fi_test : Expect read 0X5A* from parellel port register! Feb 19 08:21:02 markh2 kernel: Feb 19 08:21:02 markh2 kernel: #80 fi_test : 0X5A was read from parellel port register! Unfortunately, the test run still has lots of failures. ************Start FITH test at 07:47:50 19-02-03 Wednesday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test passed IO_address_overrange test passed MMIO_address_zero test passed MMIO_address_overrange test passed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test passed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 07:48:06 19-02-03 Wednesday!********** Here is my /var/log/messages output if it helps. Feb 19 07:47:45 markh2 kernel: #0 fi_test : mmio_address = d88fc000 Feb 19 07:47:50 markh2 kernel: FI_TEST: 1 jiffies = 197742 Feb 19 07:47:50 markh2 kernel: #2 fi_test : COMMAND_IO_READ Feb 19 07:47:50 markh2 kernel: #3 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #4 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: FI_TEST: 5 jiffies = 197825 Feb 19 07:47:50 markh2 kernel: #6 fi_test : COMMAND_IO_READW Feb 19 07:47:50 markh2 kernel: #7 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #8 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: FI_TEST: 9 jiffies = 197909 Feb 19 07:47:50 markh2 kernel: #10 fi_test : COMMAND_IO_READL Feb 19 07:47:50 markh2 kernel: #11 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #12 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 13 jiffies = 197993 Feb 19 07:47:51 markh2 kernel: #14 fi_test : COMMAND_IO_WRITE Feb 19 07:47:51 markh2 kernel: #15 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #16 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 17 jiffies = 198076 Feb 19 07:47:51 markh2 kernel: #18 fi_test : COMMAND_IO_WRITEW Feb 19 07:47:51 markh2 kernel: #19 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #20 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 21 jiffies = 198161 Feb 19 07:47:51 markh2 kernel: #22 fi_test : COMMAND_IO_WRITEL Feb 19 07:47:51 markh2 kernel: #23 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #24 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 25 jiffies = 198252 Feb 19 07:47:51 markh2 kernel: #26 fi_test : COMMAND_MMIO_READ Feb 19 07:47:51 markh2 kernel: #27 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #28 fi_test : 0X5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 29 jiffies = 198336 Feb 19 07:47:51 markh2 kernel: #30 fi_test : COMMAND_MMIO_READW Feb 19 07:47:51 markh2 kernel: #31 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #32 fi_test : 0X5A5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 33 jiffies = 198420 Feb 19 07:47:51 markh2 kernel: #34 fi_test : COMMAND_MMIO_READL Feb 19 07:47:51 markh2 kernel: #35 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #36 fi_test : 0X5A5A5A5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 37 jiffies = 198504 Feb 19 07:47:51 markh2 kernel: #38 fi_test : COMMAND_MMIO_WRITE Feb 19 07:47:51 markh2 kernel: #39 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #40 fi_test : 0X5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 41 jiffies = 198589 Feb 19 07:47:51 markh2 kernel: #42 fi_test : COMMAND_MMIO_WRITEW Feb 19 07:47:51 markh2 kernel: #43 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #44 fi_test : 0X5A5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 45 jiffies = 198673 Feb 19 07:47:51 markh2 kernel: #46 fi_test : COMMAND_MMIO_WRITEL Feb 19 07:47:51 markh2 kernel: #47 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #48 fi_test : 0X5A5A5A5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: trigger_ctl_store: Invalid command format: add, 8 tokens found Feb 19 07:47:51 markh2 kernel: FI_TEST: 49 jiffies = 198788 Feb 19 07:47:51 markh2 kernel: #50 fi_test : COMMAND_IO_READ Feb 19 07:47:51 markh2 kernel: #51 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #52 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: del_trigger_by_name: trigger precondition does not exist Feb 19 07:47:51 markh2 kernel: add_trigger: Unable to arm the trigger, unregister skip_pattern Feb 19 07:47:51 markh2 kernel: FI_TEST: 53 jiffies = 198904 Feb 19 07:47:51 markh2 kernel: #54 fi_test : COMMAND_IO_READ Feb 19 07:47:51 markh2 kernel: #55 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #56 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger skip_pattern does not exist Feb 19 07:47:52 markh2 kernel: add_trigger: Unable to arm the trigger, unregister stop_pattern Feb 19 07:47:52 markh2 kernel: FI_TEST: 57 jiffies = 199047 Feb 19 07:47:52 markh2 kernel: #58 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #59 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #60 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger stop_pattern does not exist Feb 19 07:47:52 markh2 kernel: trigger_ctl_store: Invalid command format: add, 11 tokens found Feb 19 07:47:52 markh2 kernel: FI_TEST: 61 jiffies = 199161 Feb 19 07:47:52 markh2 kernel: #62 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #63 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #64 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger hw_protected does not exist Feb 19 07:47:52 markh2 kernel: add_trigger: Unable to arm the trigger, unregister no_action Feb 19 07:47:52 markh2 kernel: FI_TEST: 65 jiffies = 199275 Feb 19 07:47:52 markh2 kernel: #66 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #67 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #68 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger no_action does not exist Feb 19 07:47:53 markh2 kernel: add_trigger: Unable to arm the trigger, unregister io_overrange Feb 19 07:47:56 markh2 kernel: add_trigger: Unable to arm the trigger, unregister 8_16 Feb 19 07:47:56 markh2 kernel: FI_TEST: 69 jiffies = 203528 Feb 19 07:47:56 markh2 kernel: #70 fi_test : COMMAND_IO_READW Feb 19 07:47:56 markh2 kernel: #71 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:56 markh2 kernel: Feb 19 07:47:56 markh2 kernel: #72 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:56 markh2 kernel: Feb 19 07:47:56 markh2 kernel: del_trigger_by_name: trigger 8_16 does not exist Feb 19 07:47:57 markh2 kernel: FI_TEST: 73 jiffies = 204636 Feb 19 07:47:57 markh2 kernel: #74 fi_test : COMMAND_MMIO_READL Feb 19 07:47:57 markh2 kernel: #75 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:57 markh2 kernel: Feb 19 07:47:57 markh2 last message repeated 5 times Feb 19 07:47:57 markh2 kernel: #76 fi_test : 0X5A5AEF23 was read from MMI/O address Feb 19 07:47:58 markh2 kernel: add_trigger: Unable to arm the trigger, unregister two_in_one1 Feb 19 07:47:58 markh2 kernel: add_trigger: Unable to arm the trigger, unregister two_in_one2 Feb 19 07:47:59 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid1 Feb 19 07:48:00 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid2 Feb 19 07:48:01 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid3 -- Mark Haverkamp <ma...@os...> |
|
From: Wang, S. <sta...@in...> - 2003-02-19 09:38:05
|
=20 -----Original Message----- From: Gao, Kevin=20 Sent: 2003-02-19 17:01 To: Zhuang, Louis; Wang, Frank; Wang, Stanley Subject: e100 frame reception test result draft. E100 frame reception test has been done, the result draft is as follow: any comment? :) =20 -Kevin =20 1. Set =A1=AES=A1=AF bit of RFD which is under received when driver = reads the SCB status register. Driver always send a RU_START command.=20 =20 OK. The e100 driver checks the hardware status and reacts properly :) =20 2. Set =A1=AES=A1=AF bit of RFD which has been received when driver = reads the SCB status register. Driver ignores the operation.=20 =20 OK. The 'S' bit is set by driver and read by hardware. Hence the driver doesn't care it.=20 <?xml:namespace prefix =3D o ns =3D = "urn:schemas-microsoft-com:office:office" /> 3. Set both =A1=AEC=A1=AF and =A1=AEOK=A1=AF bit of RFD to zero = when driver reads the SCB status register, the network cannot start, and driver will hanged, = a timeout will throw out.=20 If the 'C' bit equals zero, the driver will treat this rfd as an = incomplete packet and just wait untile 'C' equals one.=20 =20 4. Set =A1=AEC=A1=AF bit of RFD to 0, and set =A1=AEOK=A1=AF bit of = RFD to 1 when driver reads the SCB status register, the result is the same as process 2.=20 =20 process 2 or 3 ? =20 =20 5. Set =A1=AEC=A1=AF bit of RFD to 1, and set =A1=AEOK=A1=AF bit of = RFD to 0 when driver reads the SCB status register, the result is the same as process 2.=20 =20 process 2 or 3 ?=20 =20 6. Set =A1=AECRC=A1=AF bit of RFD to 1 when driver reads the SCB = status register, the driver ignores this operation.=20 =20 The driver should check this bit. =20 =20 7. Set =A1=AEAlignment error=A1=AF bit of RFD to 1 when driver = reads the SCB status register, the driver ignores this operation.=20 =20 The driver should check this bit.=20 =20 8. Set =A1=AERun out of buffer=A1=AF bit of RFD to 1 when driver = reads the SCB status register, the driver ignores this operation. =20 The driver should check this bit. 9. Set =A1=AEFrame too short=A1=AF bit of RFD to 1 when driver = reads the SCB status register, the driver ignores this operation. The driver should check this bit. =20 =20 =20 |
|
From: Louis Z. <lou...@li...> - 2003-02-19 09:35:21
|
DBP and DR need kprobes so they are broken since 2.5.60 because of the lack of up-to-date kprobes patch. - Louis On Wed, 2003-02-19 at 17:32, Louis Zhuang wrote: > Now 2.5-fi1 includes FI core, KMMIO, pf interceptor, KIRQ, fake IRQ > interceptor, code segments and testing. All stuffs do NOT depend on > kprobes. > - Louis > On Wed, 2003-02-19 at 17:09, Stanley Wang wrote: > > FYI. > > > > Best Regards, > > -Stan |
|
From: Louis Z. <lou...@li...> - 2003-02-19 09:33:06
|
Now 2.5-fi1 includes FI core, KMMIO, pf interceptor, KIRQ, fake IRQ interceptor, code segments and testing. All stuffs do NOT depend on kprobes. - Louis On Wed, 2003-02-19 at 17:09, Stanley Wang wrote: > FYI. > > Best Regards, > -Stan |
|
From: Stanley W. <sta...@li...> - 2003-02-19 09:13:49
|
FYI. Best Regards, -Stan -- Opinions expressed are those of the author and do not represent Intel Corporation |
|
From: Louis Z. <lou...@li...> - 2003-02-19 01:02:52
|
-----Forwarded Message----- > From: Louis Zhuang <lou...@li...> > To: Rusty Lynch <ru...@li...> > Cc: FITHML, Frank Wang <fra...@in...> > Subject: Re: [Fault-injection-developer] Remove kprobes dependency of kprobes? > Date: 19 Feb 2003 08:53:09 +0800 > > On Wed, 2003-02-19 at 02:22, Rusty Lynch wrote: > > > It case that was as clear as mud, our bk trees (with the current kprobes > > dependency) would look like: > > > > http://linux.bkbits.net:8080/linux-2.5 > > || > > ||------------------------------------------------ > > || || > > \/(pulls from) || > > bk://fau...@fa.../fi || > > || \/ (pulls from) > > || bk://fau...@fa.../kprobes > > || || > > || || > > \/(pulls from) \/(pulls from) > > bk://fau...@fa.../fi-kprobes > Cool! It is already a truth in my local development machine. I'd like to > see that... IMHO, I'd like to split more trees, for example, > original linux-2.5 =======> fi1 ===============|| > || ||===> fi-all > ||==> kprobes ==> fi2 ===|| > > fi1 tree is the FITH stuffs independent, fi2 tree is FITH stuffs > dependent on kprobes, fi-all is only an integrated tree. > > - Louis > -- 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 |
|
From: Louis Z. <lou...@li...> - 2003-02-19 00:37:03
|
On Wed, 2003-02-19 at 00:49, Mark Haverkamp wrote: > OK, I assume that what you want showed up in dmesg. If this isn't the > right data let me know where to look. > > > > FI_TEST: 309 jiffies = 90033991 > #310 fi_test : COMMAND_IO_READ > #311 fi_test : Expect read 0X5A* from parellel port register! > > #312 fi_test : 0XFF was read from parellel port register! Oh... it is the evil. fi_test assume your parellel is on 0x378. your can change the port address in fi_test.c:36 - Louis |
|
From: Rusty L. <ru...@li...> - 2003-02-18 18:23:42
|
On Sun, 2003-02-16 at 22:25, Louis Zhuang wrote: > Dear all, > I found the current linux kernel had changed debug exception from trap > gate to interrupt gate. It is the only reason that KMMIO depends on > Kprobes. Pls take a look at following dependency diagrams: > > Original dependency [2.5.44, 2.5.59] > 2.5<--- KIRQ > | > |- Kprobes<--- KMMIO<- Page Fault Interceptor > | > |- DBP Interceptor > | > |- DR Interceptor > > Current dependency [2.5.60, future) > 2.5<--- KIRQ > | > |- KMMIO<--- Page Fault Interceptor > | > |- Kprobes<--- DBP Interceptor > | > |- DR Interceptor > > So my questions are, > 1. Should we remove Kprobes and DBP/DR from our FITH tree and change > KMMIO against 2.5.60? > 2. Should we port Kprobes to 2.5.60 or wait Kprobes team to do it? > 3. When/How should we make DBP/DR back? > > See also http://www.uwsg.iu.edu/hypermail/linux/kernel/0302.1/0081.html > -- > Yours truly, > Louis Zhuang To be honest I am a little torn on which direction is the best direction. My take on our current situation is: * I do not think that any code created in this project (core fi infrastructure/fi components like interceptors/kirq/kmmio) should be included into the kernel until 2.7 since the current 2.5 work really should be concentrating on stabilizing for 2.6. * When it is appropriate to start feeding changes into the kernel, we will need to have clean bk trees for Linus to pull from. Any code that still has external dependencies is by definition not ready for Linus to pull into his tree. * I like having a common tree for all of us to check our current hacks into, but it is a pain to keep external dependencies updated. hmmm... how about we maintain 1 + 2n kernel trees? One tree is a clone of Linus' 2.5 tree and contains our changes that do not have external dependencies. For each external dependency we maintain two trees, the first would be a clone of Linus's tree with the external dependency changes applied, the second tree is a clone of our linux-2.5 tree with changes from the external dependencies tree pulled in and then our changes on top. It case that was as clear as mud, our bk trees (with the current kprobes dependency) would look like: http://linux.bkbits.net:8080/linux-2.5 || ||------------------------------------------------ || || \/(pulls from) || bk://fau...@fa.../fi || || \/ (pulls from) || bk://fau...@fa.../kprobes || || || || \/(pulls from) \/(pulls from) bk://fau...@fa.../fi-kprobes Using this approach, our fi tree would eventually be the tree that we ask Linus to pull from, and the I would expect that as soon as kprobes is accepted in Linus' tree that our work in fi-kprobes would move to our fi tree and the fi-kprobes and kprobes tree would go away. This approach would also discourage adding more external dependencies (which I believe is a "good thing") because it is a lot more work. For example if kprobes becomes difficult to keep current, then the fi-kprobes tree would start moving slower. Anyone who feels a strong need to depend on kpobes (or any other external dependency) would take on the maintenance of the given external tree. IMHO this seems like a fairly practical solution. Any thoughts? --rustyl |
|
From: Mark H. <ma...@os...> - 2003-02-18 16:50:17
|
On Tue, 2003-02-18 at 08:39, Gao, Kevin wrote: > Thank you for your comment, I will try to use mount command to > catch the sysfs. > But most important is that why test is failure. > After you insert the modules fi_test, > use command: > # echo "read byte" > /sys/fith_test/io, > Is there any information in ringbuffer? > Could you give me the information? OK, I assume that what you want showed up in dmesg. If this isn't the right data let me know where to look. FI_TEST: 309 jiffies = 90033991 #310 fi_test : COMMAND_IO_READ #311 fi_test : Expect read 0X5A* from parellel port register! #312 fi_test : 0XFF was read from parellel port register! -- Mark Haverkamp <ma...@os...> |
|
From: Gao, K. <kev...@in...> - 2003-02-18 16:41:35
|
Thank you for your comment, I will try to use mount command to catch the sysfs. But most important is that why test is failure. After you insert the modules fi_test, use command: # echo "read byte" > /sys/fith_test/io, Is there any information in ringbuffer? Could you give me the information? -----Original Message----- From: Mark Haverkamp [mailto:ma...@os...] Sent: 2003?2?19? 0:01 To: Gao, Kevin Cc: 'Louis Zhuang'; FITHML Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. On Tue, 2003-02-18 at 07:40, Gao, Kevin wrote: > In test script, I do not know the user's sysfs directory. > But I need echo command to sysfs file. So I use /sys > as default directory. > > Is everything is OK. > I will update code soon and make the test code clean. > > -Kevin I'm not sure what you mean. I have been mounting the sysfs directory as /sys and got the test failures. Also, in your test script you could use the mount command to see where the sysfs filesystem was mounted and use that path. For instance: # mount ... sysfs on /sys type sysfs (rw) Mark. > > -----Original Message----- > From: Mark Haverkamp [mailto:ma...@os...] > Sent: 2003?2?18? 23:25 > To: Gao, Kevin > Cc: 'Louis Zhuang'; FITHML > Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. > > > On Mon, 2003-02-17 at 16:39, Gao, Kevin wrote: > > I want to know which directory that you mount the "sysfs". > > In our test case, the directory of "sysfs" should be /sys. > > Have you mounted the "sysfs" to directory "/sys"? > > > > > > -Kevin > > Yes, I saw in the code that it was looking in /sys. > > > Mark. -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-18 16:01:51
|
On Tue, 2003-02-18 at 07:40, Gao, Kevin wrote: > In test script, I do not know the user's sysfs directory. > But I need echo command to sysfs file. So I use /sys > as default directory. > > Is everything is OK. > I will update code soon and make the test code clean. > > -Kevin I'm not sure what you mean. I have been mounting the sysfs directory as /sys and got the test failures. Also, in your test script you could use the mount command to see where the sysfs filesystem was mounted and use that path. For instance: # mount ... sysfs on /sys type sysfs (rw) Mark. > > -----Original Message----- > From: Mark Haverkamp [mailto:ma...@os...] > Sent: 2003?2?18? 23:25 > To: Gao, Kevin > Cc: 'Louis Zhuang'; FITHML > Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. > > > On Mon, 2003-02-17 at 16:39, Gao, Kevin wrote: > > I want to know which directory that you mount the "sysfs". > > In our test case, the directory of "sysfs" should be /sys. > > Have you mounted the "sysfs" to directory "/sys"? > > > > > > -Kevin > > Yes, I saw in the code that it was looking in /sys. > > > Mark. -- Mark Haverkamp <ma...@os...> |
|
From: Gao, K. <kev...@in...> - 2003-02-18 15:43:09
|
In test script, I do not know the user's sysfs directory. But I need echo command to sysfs file. So I use /sys as default directory. Is everything is OK. I will update code soon and make the test code clean. -Kevin -----Original Message----- From: Mark Haverkamp [mailto:ma...@os...] Sent: 2003?2?18? 23:25 To: Gao, Kevin Cc: 'Louis Zhuang'; FITHML Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. On Mon, 2003-02-17 at 16:39, Gao, Kevin wrote: > I want to know which directory that you mount the "sysfs". > In our test case, the directory of "sysfs" should be /sys. > Have you mounted the "sysfs" to directory "/sys"? > > > -Kevin Yes, I saw in the code that it was looking in /sys. Mark. > > > -----Original Message----- > From: Mark Haverkamp [mailto:ma...@os...] > Sent: 2003?2?18? 2:50 > To: Gao, Kevin > Cc: 'Louis Zhuang'; FITHML > Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. > > > On Mon, 2003-02-17 at 08:09, Mark Haverkamp wrote: > > On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > > > I have update the test script again, for how to using it is as following > > > process. > > > > > > 1. mount sysfs > > > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > > > Then use command ./TEST_SUITE. > > > > > > I hope everything is OK :) > > > > > > -Kevin > > > > That is pretty much what I had done. I tried again with the new test > > script and just loaded the modules in your list. Results following. > > They look similar as before. > > > > Mark. > > > > I found one of my problems. I had installed ficl in /usr/local/bin and > the scripts assume that it is in /usr/local/sbin. I got a couple of > cases to pass, but most still fail. > > > Mark. > > > > ************Start FITH test at 10:42:24 17-02-03 Monday!************ > ------------------------------------------------------------------- > Original PPIO readb function works abnormally! > Test abandoned! > Original PPIO readw function works abnormally! > Test abandoned! > Original PPIO readl function works abnormally! > Test abandoned! > Original PPIO writeb function works abnormally! > Test abandoned! > Original PPIO writew function works abnormally! > Test abandoned! > Original PPIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Original MMIO readb function works abnormally! > Test abandoned! > Original MMIO readw function works abnormally! > Test abandoned! > Original MMIO readl function works abnormally! > Test abandoned! > Original MMIO writeb function works abnormally! > Test abandoned! > Original MMIO writew function works abnormally! > Test abandoned! > Original MMIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Precondition function test failed! > Test abandoned! > Skip function test failed! > Test abandoned! > Stop function test failed! > Test abandoned! > Protection_mask function test failed! > Test abandoned! > No corrupt action function test failed! > Test abandoned! > ------------------------------------------------------------------- > IO_address_zero test passed > IO_address_overrange test passed > MMIO_address_zero test passed > MMIO_address_overrange test passed > Corrupt 8 bit to 16 bit test failed > Corrupt 16 bit to 32 bit test failed > Same trigger in one faultset test passed > Invalid trigger mode (HZ) test failed > Invalid trigger mode (skip) test failed > Invalid trigger mode (stop) test failed > ------------------------------------------------------------------- > **********FITH FUNCTIONALITY TEST RESULT********** > > Original I/O read function works abnormally! > Original I/O write function works abnormally! > Original MMI/O read function works abnormally! > Original MMI/O write function works abnormally! > Faultset preconditon test failed! > Faultset trigger skip test failed! > Faultset stop pattern test failed! > Faultset hardware protect test failed! > Trigger without action test failed! > The whole boundary test failed! > > ************************************************** > > **********Complete FITH test at 10:42:40 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-18 15:25:52
|
On Mon, 2003-02-17 at 16:39, Gao, Kevin wrote: > I want to know which directory that you mount the "sysfs". > In our test case, the directory of "sysfs" should be /sys. > Have you mounted the "sysfs" to directory "/sys"? > > > -Kevin Yes, I saw in the code that it was looking in /sys. Mark. > > > -----Original Message----- > From: Mark Haverkamp [mailto:ma...@os...] > Sent: 2003?2?18? 2:50 > To: Gao, Kevin > Cc: 'Louis Zhuang'; FITHML > Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. > > > On Mon, 2003-02-17 at 08:09, Mark Haverkamp wrote: > > On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > > > I have update the test script again, for how to using it is as following > > > process. > > > > > > 1. mount sysfs > > > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > > > Then use command ./TEST_SUITE. > > > > > > I hope everything is OK :) > > > > > > -Kevin > > > > That is pretty much what I had done. I tried again with the new test > > script and just loaded the modules in your list. Results following. > > They look similar as before. > > > > Mark. > > > > I found one of my problems. I had installed ficl in /usr/local/bin and > the scripts assume that it is in /usr/local/sbin. I got a couple of > cases to pass, but most still fail. > > > Mark. > > > > ************Start FITH test at 10:42:24 17-02-03 Monday!************ > ------------------------------------------------------------------- > Original PPIO readb function works abnormally! > Test abandoned! > Original PPIO readw function works abnormally! > Test abandoned! > Original PPIO readl function works abnormally! > Test abandoned! > Original PPIO writeb function works abnormally! > Test abandoned! > Original PPIO writew function works abnormally! > Test abandoned! > Original PPIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Original MMIO readb function works abnormally! > Test abandoned! > Original MMIO readw function works abnormally! > Test abandoned! > Original MMIO readl function works abnormally! > Test abandoned! > Original MMIO writeb function works abnormally! > Test abandoned! > Original MMIO writew function works abnormally! > Test abandoned! > Original MMIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Precondition function test failed! > Test abandoned! > Skip function test failed! > Test abandoned! > Stop function test failed! > Test abandoned! > Protection_mask function test failed! > Test abandoned! > No corrupt action function test failed! > Test abandoned! > ------------------------------------------------------------------- > IO_address_zero test passed > IO_address_overrange test passed > MMIO_address_zero test passed > MMIO_address_overrange test passed > Corrupt 8 bit to 16 bit test failed > Corrupt 16 bit to 32 bit test failed > Same trigger in one faultset test passed > Invalid trigger mode (HZ) test failed > Invalid trigger mode (skip) test failed > Invalid trigger mode (stop) test failed > ------------------------------------------------------------------- > **********FITH FUNCTIONALITY TEST RESULT********** > > Original I/O read function works abnormally! > Original I/O write function works abnormally! > Original MMI/O read function works abnormally! > Original MMI/O write function works abnormally! > Faultset preconditon test failed! > Faultset trigger skip test failed! > Faultset stop pattern test failed! > Faultset hardware protect test failed! > Trigger without action test failed! > The whole boundary test failed! > > ************************************************** > > **********Complete FITH test at 10:42:40 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Gao, K. <kev...@in...> - 2003-02-18 00:41:31
|
I want to know which directory that you mount the "sysfs". In our test case, the directory of "sysfs" should be /sys. Have you mounted the "sysfs" to directory "/sys"? -Kevin -----Original Message----- From: Mark Haverkamp [mailto:ma...@os...] Sent: 2003?2?18? 2:50 To: Gao, Kevin Cc: 'Louis Zhuang'; FITHML Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. On Mon, 2003-02-17 at 08:09, Mark Haverkamp wrote: > On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > > I have update the test script again, for how to using it is as following > > process. > > > > 1. mount sysfs > > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > > Then use command ./TEST_SUITE. > > > > I hope everything is OK :) > > > > -Kevin > > That is pretty much what I had done. I tried again with the new test > script and just loaded the modules in your list. Results following. > They look similar as before. > > Mark. > I found one of my problems. I had installed ficl in /usr/local/bin and the scripts assume that it is in /usr/local/sbin. I got a couple of cases to pass, but most still fail. Mark. ************Start FITH test at 10:42:24 17-02-03 Monday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test passed IO_address_overrange test passed MMIO_address_zero test passed MMIO_address_overrange test passed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test passed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 10:42:40 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-17 18:51:19
|
On Mon, 2003-02-17 at 08:09, Mark Haverkamp wrote: > On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > > I have update the test script again, for how to using it is as following > > process. > > > > 1. mount sysfs > > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > > Then use command ./TEST_SUITE. > > > > I hope everything is OK :) > > > > -Kevin > > That is pretty much what I had done. I tried again with the new test > script and just loaded the modules in your list. Results following. > They look similar as before. > > Mark. > I found one of my problems. I had installed ficl in /usr/local/bin and the scripts assume that it is in /usr/local/sbin. I got a couple of cases to pass, but most still fail. Mark. ************Start FITH test at 10:42:24 17-02-03 Monday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test passed IO_address_overrange test passed MMIO_address_zero test passed MMIO_address_overrange test passed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test passed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 10:42:40 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-17 16:09:59
|
On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > I have update the test script again, for how to using it is as following > process. > > 1. mount sysfs > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > Then use command ./TEST_SUITE. > > I hope everything is OK :) > > -Kevin That is pretty much what I had done. I tried again with the new test script and just loaded the modules in your list. Results following. They look similar as before. Mark. [root@markh2 fi]# lsmod Module Size Used by fi_test 6472 0 - Live 0xd890e000 fi_pf 8160 0 - Live 0xd890b000 fi_dbp 8736 0 - Live 0xd8907000 fi_core 14816 2 fi_pf,fi_dbp, Live 0xd8902000 ************Start FITH test at 08:12:37 17-02-03 Monday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test failed IO_address_overrange test failed MMIO_address_zero test failed MMIO_address_overrange test failed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test failed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 08:12:52 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Louis Z. <lou...@li...> - 2003-02-17 06:28:39
|
Dear all, I found the current linux kernel had changed debug exception from trap gate to interrupt gate. It is the only reason that KMMIO depends on Kprobes. Pls take a look at following dependency diagrams: Original dependency [2.5.44, 2.5.59] 2.5<--- KIRQ | |- Kprobes<--- KMMIO<- Page Fault Interceptor | |- DBP Interceptor | |- DR Interceptor Current dependency [2.5.60, future) 2.5<--- KIRQ | |- KMMIO<--- Page Fault Interceptor | |- Kprobes<--- DBP Interceptor | |- DR Interceptor So my questions are, 1. Should we remove Kprobes and DBP/DR from our FITH tree and change KMMIO against 2.5.60? 2. Should we port Kprobes to 2.5.60 or wait Kprobes team to do it? 3. When/How should we make DBP/DR back? See also http://www.uwsg.iu.edu/hypermail/linux/kernel/0302.1/0081.html -- 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 |
|
From: Gao, K. <kev...@in...> - 2003-02-17 05:58:56
|
I have update the test script again, for how to using it is as following process. 1. mount sysfs 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" Then use command ./TEST_SUITE. I hope everything is OK :) -Kevin -----Original Message----- From: Louis Zhuang [mailto:lou...@li...] Sent: 2003?2?17? 9:07 To: Mark Haverkamp Cc: FITHML Subject: Re: [Fault-injection-developer] FITH test ABAT has updated. Thank you for your breave try ;-) Did you mount sysfs? On Sat, 2003-02-15 at 01:29, Mark Haverkamp wrote: > On Wed, 2003-02-12 at 18:49, Gao, Kevin wrote: > > Test suite has been updated, > > It includes most function test cases and boundary test cases. > > You can download at: > > > > bk://fau...@fa.../fith-tool. > > > > The ABAT's directory is in directory "fith-tool/fith_test" > > > > The function test cases are in directory > > "fith-tool/fith_test/fault_set/fun_test > > The boundary test cases are in directory > > "fith-tool/fith_test/fault_set/boundary_test. > > > > -Kevin > > > > Hi, > > I downloaded these and tried them out. I ran the ./TEST_SUITE script > and I had problems. I have included a lsmod and the test log output. > > Is there something obvious that I am doing wrong? If not, what is a good > way to go about debugging this? > > Thanks, > Mark. > > lsmod output: > > Module Size Used by > fi_test 6472 0 - Live 0xd891b000 > fi_mock_cs 2432 0 - Live 0xd890d000 > fi_mock_interceptor 3360 0 - Live 0xd8915000 > fi_irq 5728 0 - Live 0xd8912000 > fi_pf 8160 0 - Live 0xd890f000 > fi_sample_cs 3076 0 - Live 0xd88ff000 > fi_dbp 8736 0 - Live 0xd8907000 > fi_core 14816 6 fi_mock_cs,fi_mock_interceptor,fi_irq,fi_pf,fi_sample_cs,fi_dbp, Live 0xd8902000 > > > ************Start FITH test at 13:04:39 13-02-03 Thursday!************ > ------------------------------------------------------------------- > Original PPIO readb function works abnormally! > Test abandoned! > Original PPIO readw function works abnormally! > Test abandoned! > Original PPIO readl function works abnormally! > Test abandoned! > Original PPIO writeb function works abnormally! > Test abandoned! > Original PPIO writew function works abnormally! > Test abandoned! > Original PPIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Original MMIO readb function works abnormally! > Test abandoned! > Original MMIO readw function works abnormally! > Test abandoned! > Original MMIO readl function works abnormally! > Test abandoned! > Original MMIO writeb function works abnormally! > Test abandoned! > Original MMIO writew function works abnormally! > Test abandoned! > Original MMIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Precondition function test failed! > Test abandoned! > Skip function test failed! > Test abandoned! > Stop function test failed! > Test abandoned! > Protection_mask function test failed! > Test abandoned! > No corrupt action function test failed! > Test abandoned! > ------------------------------------------------------------------- > IO_address_zero test failed > IO_address_overrange test failed > MMIO_address_zero test failed > MMIO_address_overrange test failed > Corrupt 8 bit to 16 bit test failed > Corrupt 16 bit to 32 bit test failed > Same trigger in one faultset test failed > Invalid trigger mode (HZ) test failed > Invalid trigger mode (skip) test failed > Invalid trigger mode (stop) test failed > ------------------------------------------------------------------- > **********FITH FUNCTIONALITY TEST RESULT********** > > Original I/O read function works abnormally! > Original I/O write function works abnormally! > Original MMI/O read function works abnormally! > Original MMI/O write function works abnormally! > Faultset preconditon test failed! > Faultset trigger skip test failed! > Faultset stop pattern test failed! > Faultset hardware protect test failed! > Trigger without action test failed! > The whole boundary test failed! > > ************************************************** > > **********Complete FITH test at 13:04:54 13-02-03 Thursday!********** -- 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:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fault-injection-developer mailing list Fau...@li... https://lists.sourceforge.net/lists/listinfo/fault-injection-developer |
|
From: Louis Z. <lou...@li...> - 2003-02-17 01:09:24
|
Thank you for your breave try ;-) Did you mount sysfs? On Sat, 2003-02-15 at 01:29, Mark Haverkamp wrote: > On Wed, 2003-02-12 at 18:49, Gao, Kevin wrote: > > Test suite has been updated, > > It includes most function test cases and boundary test cases. > > You can download at: > > > > bk://fau...@fa.../fith-tool. > > > > The ABAT's directory is in directory "fith-tool/fith_test" > > > > The function test cases are in directory > > "fith-tool/fith_test/fault_set/fun_test > > The boundary test cases are in directory > > "fith-tool/fith_test/fault_set/boundary_test. > > > > -Kevin > > > > Hi, > > I downloaded these and tried them out. I ran the ./TEST_SUITE script > and I had problems. I have included a lsmod and the test log output. > > Is there something obvious that I am doing wrong? If not, what is a good > way to go about debugging this? > > Thanks, > Mark. > > lsmod output: > > Module Size Used by > fi_test 6472 0 - Live 0xd891b000 > fi_mock_cs 2432 0 - Live 0xd890d000 > fi_mock_interceptor 3360 0 - Live 0xd8915000 > fi_irq 5728 0 - Live 0xd8912000 > fi_pf 8160 0 - Live 0xd890f000 > fi_sample_cs 3076 0 - Live 0xd88ff000 > fi_dbp 8736 0 - Live 0xd8907000 > fi_core 14816 6 fi_mock_cs,fi_mock_interceptor,fi_irq,fi_pf,fi_sample_cs,fi_dbp, Live 0xd8902000 > > > ************Start FITH test at 13:04:39 13-02-03 Thursday!************ > ------------------------------------------------------------------- > Original PPIO readb function works abnormally! > Test abandoned! > Original PPIO readw function works abnormally! > Test abandoned! > Original PPIO readl function works abnormally! > Test abandoned! > Original PPIO writeb function works abnormally! > Test abandoned! > Original PPIO writew function works abnormally! > Test abandoned! > Original PPIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Original MMIO readb function works abnormally! > Test abandoned! > Original MMIO readw function works abnormally! > Test abandoned! > Original MMIO readl function works abnormally! > Test abandoned! > Original MMIO writeb function works abnormally! > Test abandoned! > Original MMIO writew function works abnormally! > Test abandoned! > Original MMIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Precondition function test failed! > Test abandoned! > Skip function test failed! > Test abandoned! > Stop function test failed! > Test abandoned! > Protection_mask function test failed! > Test abandoned! > No corrupt action function test failed! > Test abandoned! > ------------------------------------------------------------------- > IO_address_zero test failed > IO_address_overrange test failed > MMIO_address_zero test failed > MMIO_address_overrange test failed > Corrupt 8 bit to 16 bit test failed > Corrupt 16 bit to 32 bit test failed > Same trigger in one faultset test failed > Invalid trigger mode (HZ) test failed > Invalid trigger mode (skip) test failed > Invalid trigger mode (stop) test failed > ------------------------------------------------------------------- > **********FITH FUNCTIONALITY TEST RESULT********** > > Original I/O read function works abnormally! > Original I/O write function works abnormally! > Original MMI/O read function works abnormally! > Original MMI/O write function works abnormally! > Faultset preconditon test failed! > Faultset trigger skip test failed! > Faultset stop pattern test failed! > Faultset hardware protect test failed! > Trigger without action test failed! > The whole boundary test failed! > > ************************************************** > > **********Complete FITH test at 13:04:54 13-02-03 Thursday!********** -- 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 |
|
From: Zhuang, L. <lou...@in...> - 2003-02-14 17:34:16
|
Dear Arun,
Thank you for your interest! ;-) Please see my comments...
-----Original Message-----
From: Fan, Ardelle
Sent: Friday, February 14, 2003 4:26 PM
To: Zhuang, Louis
Subject: FW: [Hardeneddrivers-discuss] about
-----Original Message-----
From: Arun Prasad [mailto:ar...@ne...]
Sent: 2003?2?14? 16:26
To: har...@li...
Subject: [Hardeneddrivers-discuss] about
Hi all,
Iam interested in contribute (participate) in the Driver Harness
tool for Linux (FITH). I browsed through
the FITH hld and DDH-05 spec... I like to clarify the below doubts...
* Does this project still going on actively?
Yes! But we use BitKeeper instead of CVS... so you might try BK.
* Whats the current status of the project?
We've implemented several basic kernel mechanisms (KMMIO/KIRQ etc) for FI
and simple code-segment based FI logic. But the final design is not
determined.
* Can I start contributing to this project from this stage?
Any idea is really welcome!
Please clarify the doubts...
Thanks
-arun
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Hardeneddrivers-discuss mailing list
Har...@li...
https://lists.sourceforge.net/lists/listinfo/hardeneddrivers-discuss
|
|
From: Mark H. <ma...@os...> - 2003-02-14 17:30:06
|
On Wed, 2003-02-12 at 18:49, Gao, Kevin wrote: > Test suite has been updated, > It includes most function test cases and boundary test cases. > You can download at: > > bk://fau...@fa.../fith-tool. > > The ABAT's directory is in directory "fith-tool/fith_test" > > The function test cases are in directory > "fith-tool/fith_test/fault_set/fun_test > The boundary test cases are in directory > "fith-tool/fith_test/fault_set/boundary_test. > > -Kevin > Hi, I downloaded these and tried them out. I ran the ./TEST_SUITE script and I had problems. I have included a lsmod and the test log output. Is there something obvious that I am doing wrong? If not, what is a good way to go about debugging this? Thanks, Mark. lsmod output: Module Size Used by fi_test 6472 0 - Live 0xd891b000 fi_mock_cs 2432 0 - Live 0xd890d000 fi_mock_interceptor 3360 0 - Live 0xd8915000 fi_irq 5728 0 - Live 0xd8912000 fi_pf 8160 0 - Live 0xd890f000 fi_sample_cs 3076 0 - Live 0xd88ff000 fi_dbp 8736 0 - Live 0xd8907000 fi_core 14816 6 fi_mock_cs,fi_mock_interceptor,fi_irq,fi_pf,fi_sample_cs,fi_dbp, Live 0xd8902000 ************Start FITH test at 13:04:39 13-02-03 Thursday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test failed IO_address_overrange test failed MMIO_address_zero test failed MMIO_address_overrange test failed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test failed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 13:04:54 13-02-03 Thursday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Gao, K. <kev...@in...> - 2003-02-13 02:52:25
|
Test suite has been updated, It includes most function test cases and boundary test cases. You can download at: bk://fau...@fa.../fith-tool. The ABAT's directory is in directory "fith-tool/fith_test" The function test cases are in directory "fith-tool/fith_test/fault_set/fun_test The boundary test cases are in directory "fith-tool/fith_test/fault_set/boundary_test. -Kevin |
|
From: Rusty L. <ru...@li...> - 2003-02-11 00:47:30
|
On Mon, 2003-02-10 at 15:50, Mark Haverkamp wrote:
> While playing with the fi code to try and figure out how it works I ran
> across this in fi_core.c. I noticed that if I attached a trigger to a
> code segment, the opcode in the trigger didn't display anything when I
> cat'ed the file. The attached code changes print_cs_list to return the
> value from sprintf instead of unconditional zero. Also
> trigger_operand_read's seemed to have a typo in the sprintf.
>
>
> --
> Mark Haverkamp <ma...@os...>
> ----
>
Thanks, applied.
--rustyl
> ===== drivers/fi/fi_core.c 1.46 vs edited =====
> --- 1.46/drivers/fi/fi_core.c Thu Jan 23 17:10:33 2003
> +++ edited/drivers/fi/fi_core.c Mon Feb 10 15:00:40 2003
> @@ -504,7 +504,7 @@
> i += sprintf(page+i, "code segment name: %s\n",
> pos->kobj.name);
> }
> - return 0;
> + return i;
> }
>
> static ssize_t trigger_opcode_read(struct trigger * p, char * page)
> @@ -530,7 +530,7 @@
> if (list_empty(&p->cs_list)) {
> return sprintf(page,"%i\n",p->operand);
> } else {
> - return sprintf(page,"(no used)\n");
> + return sprintf(page,"(not used)\n");
> }
> }
>
|
|
From: Mark H. <ma...@os...> - 2003-02-10 23:50:21
|
While playing with the fi code to try and figure out how it works I ran across this in fi_core.c. I noticed that if I attached a trigger to a code segment, the opcode in the trigger didn't display anything when I cat'ed the file. The attached code changes print_cs_list to return the value from sprintf instead of unconditional zero. Also trigger_operand_read's seemed to have a typo in the sprintf. -- Mark Haverkamp <ma...@os...> |
25 messages has been excluded from this view by a project administrator.
