Paul Larson wrote:
>
> On Thu, 2002-10-24 at 18:23, mingming cao wrote:
> > Thanks for your quick feedback. I did LTP tests on it--it passed(well,
> > I saw a failure on shmctl(), but the failure was there since 2.5.43
> > kernel). I will do more stress tests on it soon.
> Which shmctl() test is this? To my knowledge, there are no current
> known issues with shmctl tests. There is however one with sem02 in
> semctl() that last I heard has been partially fixed in the kernel and
> still needs to be fixed in glibc. Is that the one you are referring to,
> or is there really some other shmctl test in LTP that is failing?
Here is the failure I saw on LTP test. The one failed is
/ltp-20020807/testcases/kernel/syscalls/ipc/shmctl/shmctl01
<<<test_start>>>
tag=shmctl01 stime=1035475025
cmdline="shmctl01"
contacts=""
analysis=exit
initiation_status="ok"
<<<test_output>>>
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 1 PASS : pid, size, # of attaches and mode are correct -
pass #1
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 1 PASS : pid, size, # of attaches and mode are correct -
pass #1
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 1 PASS : pid, size, # of attaches and mode are correct -
pass #1
shmctl01 2 PASS : pid, size, # of attaches and mode are correct -
pass #2
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 1 PASS : pid, size, # of attaches and mode are correct -
pass #1
shmctl01 2 PASS : pid, size, # of attaches and mode are correct -
pass #2
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 1 PASS : pid, size, # of attaches and mode are correct -
pass #1
shmctl01 2 PASS : pid, size, # of attaches and mode are correct -
pass #2
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 1 PASS : pid, size, # of attaches and mode are correct -
pass #1
shmctl01 2 PASS : pid, size, # of attaches and mode are correct -
pass #2
shmctl01 3 FAIL : # of attaches is incorrect - 0
shmctl01 4 PASS : new mode and change time are correct
<<<execution_status>>>
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>
On Fri, 2002-10-25 at 12:17, mingming cao wrote:
>
> shmctl01 3 FAIL : # of attaches is incorrect - 0
I guess you are running it with -i2? I just tried shmctl01 -i2 on a
2.5.44 kernel and did not get this error.
shmctl01 1 PASS : pid, size, # of attaches and mode are correct -
pass #1 shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 2 PASS : pid, size, # of attaches and mode are correct -
pass #2
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 3 PASS : new mode and change time are correct
shmctl01 4 PASS : shared memory appears to be removed
shmctl01 1 PASS : pid, size, # of attaches and mode are correct -
pass #1
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 2 PASS : pid, size, # of attaches and mode are correct -
pass #2
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 0 INFO : shmdt() failed - 22
shmctl01 3 PASS : new mode and change time are correct
shmctl01 4 PASS : shared memory appears to be removed
If I can find some time, I'll try to grab your patch and see if I can
reproduce the error on my machine.
-Paul Larson