From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Randolph Chung <randolph@tausq.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] what's up with the ipc syscalls?
Date: Sun, 2 Nov 2003 17:56:27 -0500 [thread overview]
Message-ID: <20031102225626.GF26916@systemhalted> (raw)
In-Reply-To: <20031102214200.GA5299@solo.franken.de>
On Sun, Nov 02, 2003 at 10:42:00PM +0100, Thomas Bogendoerfer wrote:
> On Sun, Nov 02, 2003 at 10:12:52AM -0800, Randolph Chung wrote:
> > anyway, if we are only supporting IPC_64, then why mask off the IPC64
> > bit in the wrapper? if the ipc/utils.c stuff isn't there, wouldn't it
> > default to doing the right thing when IPC_64 is set?
>
> look at the switch statements in msg.c/sem.c/shm.c. If you don't mask
> off IPC_64, the cases don't match.
>
> > right now glibc *doesn't* call the syscall with IPC_64, but i'm about to
> > make it do that again.
>
> I don't think this is a good idea, because by checking for IPC_64 we
> could see, whether an old glibc is used and could convert structs
> (see sys_parisc.c:sys_shmctl_broken()).
There is no such thing as that "old glibc" we have always had
__ASSUME_IPC64. What support are we looking to preserve?
c.
next prev parent reply other threads:[~2003-11-02 23:01 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
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 [this message]
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=20031102225626.GF26916@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.org \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.