Paul Larson wrote:
>
> 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?
No, I did not use -i2.
What I did is just run ./shmctl01
> I just tried shmctl01 -i2 on a
> 2.5.44 kernel and did not get this error.
Sorry, Paul. Could you try 2.5.44-mm4? I saw the error on clean
2.5.44-mm4(without my patch). And I remember I saw this on 2.5.42-mm2
also.
Here is what I saw:
[root@elm3b83 shmctl]# ./shmctl01
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 FAIL : # of attaches is incorrect - 0
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 4 PASS : new mode and change time are correct
[root@elm3b83 shmctl]# ./shmctl01 -i2
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 FAIL : # of attaches is incorrect - 0
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 4 PASS : new mode and change time are correct
shmctl01 1 BROK : couldn't create the shared memory segment
shmctl01 2 BROK : Remaining cases broken
shmctl01 3 BROK : Remaining cases broken
shmctl01 4 BROK : Remaining cases broken
On Fri, 2002-10-25 at 13:51, mingming cao wrote:
> Paul Larson wrote:
> >
> > 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?
> No, I did not use -i2.
Maybe I just read it wrong.
> What I did is just run ./shmctl01
>
> > I just tried shmctl01 -i2 on a
> > 2.5.44 kernel and did not get this error.
> Sorry, Paul. Could you try 2.5.44-mm4? I saw the error on clean
> 2.5.44-mm4(without my patch). And I remember I saw this on 2.5.42-mm2
> also.
>
> Here is what I saw:
I still have my results from testing 2.5.44-mm4, here's a cut and paste
from shmctl01:
<<<test_start>>>
tag=shmctl01 stime=1035486589
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 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 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 3 PASS : new mode and change time are correct
shmctl01 4 PASS : shared memory appears to be removed
<<<execution_status>>>
duration=1 termination_type=exited termination_id=0 corefile=no
cutime=0 cstime=1
<<<test_end>>>
I havn't seen this test fail before but I'll be happy to do more testing
with your patch to see if I can reproduce it. You may also want to
consider updating LTP to the newest version. I'm fairly certain that
shmctl01 hasn't been changed since the version you have, but just to be
consistent you may want to do that.
Thanks,
Paul Larson