From: Takeshi AIHANA <takeshi_aihana@montavista.co.jp>
To: linux-mips@oss.sgi.com
Subject: Re: (Re-Send) shmctl() returns corrupt value on pb1000.
Date: Mon, 03 Jun 2002 19:09:18 +0900 [thread overview]
Message-ID: <m3d6v8znap.wl@aihana> (raw)
In-Reply-To: <20020531.112847.74756483.nemoto@toshiba-tops.co.jp>
Hello,
At Fri, 31 May 2002 11:28:47 +0900 (JST),
Atsushi Nemoto wrote:
> takeshi_aihana> Is there any inconsistents on those conditions?
>
> AFAIK, Yes. For example, look struct ipc_perm in bits/ipc.h and
> struct ipc64_perm in asm-mips/ipcbuf.h (not struct ipc_perm in
> linux/ipc.h which is obsolete).
I did to check both bits/shm.h (glibc-2.2.3), bits/shm.h (glibc-2.2.4) and asm-mips/shmbuf.h
for calling shmctl();
There are any differences 'struct shmid_ds' between glibc-2.2.3 and 2.2.4 that I saw.
However, I do not think those diffs are caused this problem.
Because the 'shm_segsz` which a member of this will be allocated on same location even if the follows members
behind 'shm_segsz' are changed; i.e. it will have same value as 'shm_segsz' on both different structure.
Is this right?
> If you can. Please do not forget rebuilding all applications which
> including these headers. If you want to stay in 2.2.3, you will have
> to modify your kernel headers according to the libc headers.
I understood. It might to solve this problem as the most simple way.
Thank you for your advice.
Regards.
---
(TAKESHI - MontaVista Software)
next prev parent reply other threads:[~2002-06-03 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 11:10 (Re-Send) shmctl() returns corrupt value on pb1000 Takeshi Aihana
2002-05-30 12:19 ` Atsushi Nemoto
2002-05-30 13:02 ` Takeshi Aihana
2002-05-31 2:28 ` Atsushi Nemoto
2002-06-03 10:09 ` Takeshi AIHANA [this message]
2002-06-03 12:49 ` Atsushi Nemoto
2002-06-04 3:14 ` Takeshi AIHANA
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=m3d6v8znap.wl@aihana \
--to=takeshi_aihana@montavista.co.jp \
--cc=linux-mips@oss.sgi.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