All of lore.kernel.org
 help / color / mirror / Atom feed
From: JSO <soete.joel@tiscali.be>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Randolph Chung <randolph@tausq.org>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] what's up with the ipc syscalls?
Date: Wed, 12 Nov 2003 19:54:14 +0000	[thread overview]
Message-ID: <3FB28FE6.2040908@tiscali.be> (raw)
In-Reply-To: <20031111214610.GJ18512@systemhalted>

Carlos O'Donell wrote:

>>I had some thoughts about the conversion stuff, I've added to work
>>around problems introduced because of the change of some structures in
>>glibc/kernel. I finally realized, that these conversion only works,
>>if the "old glibc" is still installed together with the old binary.
>>That's because the newer glibcs don't set the IPC_64 bit when doing 
>>the syscall, but the old binary still uses the wrong structs, so the
>>conversion routine never triggers. I think it's really time to remove that
>>crap. Below is an compiled but not booted patch, which removes it and also
>>forward ports the necessary bits in ipc/util.c from 2.4. 
>>    
>>
>
>The following things confuse me.
>
>a. Our glibc never set IPC_64, we had pass-thru assembly syscall
>   wrappers. Why? Because we don't have an IPC multiplexor, none of the
>   generic glibc code can be used by hppa.
>
>So I don't understand some of your comments about "old glibc setting
>IPC_64."
>
>  
>
>>If someone also wants to change glibc, feel free. I still think changing
>>glibc is a bad idea, because this new glibc won't work with a current 2.4
>>kernel.
>>    
>>
>
>I believed we had the following scenario:
>
>a. Old glibc never called with IPC_64.
>b. Kernel turned IPC_64 on for us so we get the new style structs.
>c. Apps get new style structs without calling IPC_64.
>
>Now we wish to have the hack in the kernel removed, but apps exist that
>expect newstyle structs without calling IPC_64. Thus glibc has to
>call the syscall with IPC_64 to get the right value back to userspace.
>
>AFAIK the following is required:
>
>a. Remove kernel hacks (Thanks Thomas!).
>  
>
So I test it successfuly with 2.4 on my b2k (just re-compile the kernel, 
ssh remote connection, rsync ft, ...) :)
Sorry no more time try 2.6 on a b180 :(

>b. Add glibc code to turn IPC_64 on for all the afflicted syscalls.
>c. Eventually when all the apps disappear we can toss out the code from
>   glibc.
>
>Thomas, did I get this right?
>
>Cheers,
>Carlos.
>
>_______________________________________________
>parisc-linux mailing list
>parisc-linux@lists.parisc-linux.org
>http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>  
>

      parent reply	other threads:[~2003-11-12 19:54 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
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 [this message]

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=3FB28FE6.2040908@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=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.