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 13:20:42 -0500 [thread overview]
Message-ID: <1035570043.5646.191.camel@plars> (raw)
In-Reply-To: <3DB97C90.2DF810E6@us.ibm.com>
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
next prev parent reply other threads:[~2002-10-25 18:24 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 [this message]
2002-10-25 18:51 ` mingming cao
2002-10-25 19:06 ` Paul Larson
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=1035570043.5646.191.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