From: buhr@stat.wisc.edu (Kevin Buhr)
To: Christoph Rohland <cr@sap.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test5 bug: invalid "shmid_kernel" passed to "shm_nopage_core"
Date: 19 Dec 2000 12:11:52 -0600 [thread overview]
Message-ID: <vbaelz4qo0n.fsf@mozart.stat.wisc.edu> (raw)
In-Reply-To: <vbaaeapf4ti.fsf@mozart.stat.wisc.edu> <m3g0kggydi.fsf@linux.local> <vbay9y7dxgr.fsf@mozart.stat.wisc.edu> <m37l5rggmm.fsf@linux.local> <vbasnoeeajg.fsf@mozart.stat.wisc.edu> <qww1yv4bxdg.fsf@sap.com>
In-Reply-To: Christoph Rohland's message of "19 Dec 2000 09:58:51 +0100"
Christoph Rohland <cr@sap.com> writes:
>
> I am just running a stress test on 2.4.0-test13-pre3 + appended patch
> without problems. Is the shm segment deleted sometimes or is it always
> the same segment?
IIRC, in my particular crash case, the Enlightenment window manager
was using the X shared memory extension to take snapshots of the
screen for its little desktop pager window around 30 times a second;
Mozilla was also sharing some memory with the X server for something.
The code in Enlightenment did a complete shmget/shmat/shmctl(RMID)/shmdt
cycle, so that segment *was* being constantly deleted. The Mozilla
ones stuck around. The particular address that was being reference in
the shm_nopage_core call corresponded to the segments being created
and deleted by Enlightenment, however.
Thanks for the locking tutorial, too.
Kevin <buhr@stat.wisc.edu>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-19 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 21:17 Kevin Buhr
2000-11-25 10:05 ` Christoph Rohland
2000-11-26 7:05 ` Kevin Buhr
2000-11-26 10:41 ` Christoph Rohland
2000-11-26 20:35 ` Kevin Buhr
2000-12-19 8:58 ` Christoph Rohland
2000-12-19 18:11 ` Kevin Buhr [this message]
2000-12-20 7:30 ` Christoph Rohland
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=vbaelz4qo0n.fsf@mozart.stat.wisc.edu \
--to=buhr@stat.wisc.edu \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®