From: Paul Larson <plars@linuxtestproject.org>
To: cmm@us.ibm.com
Cc: Andrew Morton <akpm@digeo.com>, Hugh Dickins <hugh@veritas.com>,
manfred@colorfullife.com, lkml <linux-kernel@vger.kernel.org>,
dipankar@in.ibm.com, lse-tech <lse-tech@lists.sourceforge.net>
Subject: Re: [Lse-tech] Re: [PATCH]updated ipc lock patch
Date: 25 Oct 2002 14:06:59 -0500 [thread overview]
Message-ID: <1035572820.5646.211.camel@plars> (raw)
In-Reply-To: <3DB992B7.E8919930@us.ibm.com>
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
next prev parent reply other threads:[~2002-10-25 19:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 0:14 [PATCH]IPC locks breaking down with RCU mingming cao
2002-10-20 13:14 ` Hugh Dickins
2002-10-20 17:27 ` Hugh Dickins
2002-10-21 18:11 ` mingming cao
2002-10-21 19:00 ` Hugh Dickins
2002-10-24 21:49 ` [PATCH]updated ipc lock patch mingming cao
2002-10-24 22:29 ` Andrew Morton
2002-10-24 22:56 ` Hugh Dickins
2002-10-24 23:30 ` Andrew Morton
2002-10-24 23:59 ` Hugh Dickins
2002-10-25 0:35 ` [Lse-tech] " Rick Lindsley
2002-10-25 1:07 ` Robert Love
2002-10-25 0:07 ` mingming cao
2002-10-25 0:24 ` Andrew Morton
2002-10-25 4:18 ` Rusty Russell
2002-10-25 5:53 ` mingming cao
2002-10-25 7:27 ` Rusty Russell
2002-10-25 5:36 ` Manfred Spraul
2002-10-25 16:53 ` Rik van Riel
2002-10-24 23:23 ` mingming cao
2002-10-25 14:21 ` [Lse-tech] " Paul Larson
2002-10-25 17:17 ` mingming cao
2002-10-25 18:20 ` Paul Larson
2002-10-25 18:51 ` mingming cao
2002-10-25 19:06 ` Paul Larson [this message]
2002-10-25 20:14 ` mingming cao
2002-10-25 20:23 ` Manfred Spraul
2002-10-25 0:38 ` Cliff White
2002-10-31 17:52 ` [Lse-tech] Re: [PATCH]updated ipc lock patch [PERFORMANCE RESULTS] Bill Hartner
2002-10-21 19:18 ` [PATCH]IPC locks breaking down with RCU Dipankar Sarma
2002-10-21 19:36 ` Hugh Dickins
2002-10-21 19:41 ` mingming cao
2002-10-21 20:14 ` Dipankar Sarma
2002-10-21 18:07 ` mingming cao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1035572820.5646.211.camel@plars \
--to=plars@linuxtestproject.org \
--cc=akpm@digeo.com \
--cc=cmm@us.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).