From: "Tom Brusehaver (N-Sysdyne Corporation)" <Thomas.Brusehaver@lmco.com>
To: linux-kernel@vger.kernel.org
Subject: shm_open doesn't work (fix maybe).
Date: Tue, 24 Apr 2001 11:46:20 -0500 [thread overview]
Message-ID: <3AE5ADDC.A7AA6F51@lmco.com> (raw)
I have been chasing all around trying to find out why
shm_open always returns ENOSYS. It is implemented
in glibc-2.2.2, and seems the 2.4.3 kernel knows about
shmfs.
It seems the file linux/mm/shmem.c has:
#define SHMEM_MAGIC 0x01021994
And the glibc-2.2.2/sysdeps/unix/sysv/linux/linux_fsinfo.h has:
#define SHMFS_SUPER_MAGIC 0x02011994
Well, which is correct?
Looking for (trouble?) the reason, I found a patch
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg16996.html
where there seems to be a typo, the remove line is correct:
-#define SHM_FS_MAGIC 0x02011994
but the insert line has the 0201 reversed:
+#define SHMEM_MAGIC 0x01021994
Has anyone else run into this? (It seems the documentation on shmfs
is sparse, so I don't think too many folks are even messing with it).
Initially I thought, hey simple, just fix the kernel source, and
everyone will be happy. But, then I thought, ooof! code I build
for someone without a patched kernel will surely break. So then
I thought simple I'll fix glibc and statically link. Of course, then
someone will fix this, and all my binaries will be broken.
Help! what is the "right" fix.
next reply other threads:[~2001-04-24 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 16:46 Tom Brusehaver (N-Sysdyne Corporation) [this message]
2001-04-24 17:01 ` shm_open doesn't work (fix maybe) Jakub Jelinek
2001-04-25 7:08 ` 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=3AE5ADDC.A7AA6F51@lmco.com \
--to=thomas.brusehaver@lmco.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