From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Randolph Chung <tausq@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] what's up with the ipc syscalls?
Date: Sun, 2 Nov 2003 19:01:50 +0100 [thread overview]
Message-ID: <20031102180150.GA14554@solo.franken.de> (raw)
In-Reply-To: <20031101082451.GJ28967@tausq.org>
On Sat, Nov 01, 2003 at 12:24:51AM -0800, Randolph Chung wrote:
> in our syscall table, semctl, msgctl and shmctl are marked as "broken".
> Does anybody know what's up with that?
>
> i did a simple hack, which is to replace
>
> return sys_msgctl (msqid, cmd & ~IPC_64, buf);
>
> with
>
> return sys_msgctl (msqid, cmd | IPC_64, buf);
>
> in sys_parisc.c, and at least in some simple tests it seems to work
> (whereas the original one was really broken)
if this makes a difference, something in ipc/util.c is missing. When I
added the code above, I also made the ipc_parse_version only return
IPC_64, because we never had IPC_OLD. Older glibc made the call with
IPC_64 set, so we needed the wrapper in sys_parisc.c. I just looked
at the 2.4 version of ipc/util.c and it's still ok ...
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ Alexander Viro on linux-kernel ]
next prev parent reply other threads:[~2003-11-02 18:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 8:24 [parisc-linux] what's up with the ipc syscalls? Randolph Chung
2003-11-02 18:01 ` Thomas Bogendoerfer [this message]
2003-11-02 18:12 ` Randolph Chung
2003-11-02 21:42 ` Thomas Bogendoerfer
2003-11-02 21:55 ` Randolph Chung
2003-11-03 8:59 ` Thomas Bogendoerfer
2003-11-02 22:56 ` Carlos O'Donell
2003-11-03 8:56 ` Thomas Bogendoerfer
2003-11-03 21:41 ` Carlos O'Donell
2003-11-10 23:44 ` Thomas Bogendoerfer
2003-11-11 20:41 ` Joel Soete
2003-11-11 21:46 ` Carlos O'Donell
2003-11-12 15:32 ` Thomas Bogendoerfer
2003-11-14 0:35 ` Carlos O'Donell
2003-11-12 19:54 ` JSO
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=20031102180150.GA14554@solo.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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