Re: [parisc-linux] what's up with the ipc syscalls?

[Carlos O'Donell <carlos@baldric.uwo.ca>]

On Mon, Nov 03, 2003 at 09:56:01AM +0100, Thomas Bogendoerfer wrote:
> glibc 2.2.x, some weeks before woody went final. For a closer date
> check the date of my sys_parisc.c commit.

My apologies Thomas I think I begin to see your logic. Now if you follow
me I'll paint a picture.

a. We don't have an IPC multiplexor.
b. We added all such functions into syscalls.list so they would be
   generated as assembly wrappers.
c. Kernel would activate IPC64 for all the calls so it returned IPC64 to
   userspace.

> Since there might be still binaries in woody, which are compiled
> with an such an "old" glibc, we will break this binaries. The suggested
> change is an change of the kernel ABI, so I would avoid it. The problem
> with this "old" glibc was, that the structs for shmctl and friends
> weren't properly aligned for 64bit. I've changed that and also decided
> to get rid of IPC_64, because that's x86 crap.
> 
> Adding the 2.4 changes to the 2.6 kernel should fix everything.

Should an old binary exist with this old glibc, it would break should
the kernel stop activating IPC64.

I agree that the 2.4 changes forward ported will change everything, but
the glibc changes are *also* required so we can eventually turn off the
kernel code that activates IPC64 for all the incoming calls. When we
don't care about these old binaries and old glibc we will remove the
kernel code.

Now it's my turn to ask the question: Did that make any sense? :o)

c.