Received: (qmail 5581 invoked by uid 2012); 11 Aug 1998 17:56:01 -0000 Message-Id: <19980811175601.5580.qmail@hyperreal.org> Date: 11 Aug 1998 17:56:01 -0000 From: Greg McGurk Reply-To: gregm@t3.com To: apbugs@hyperreal.org Subject: wrong client ip address in access log X-Send-Pr-Version: 3.2 >Number: 2829 >Category: os-irix >Synopsis: wrong client ip address in access log >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Aug 11 11:00:01 PDT 1998 >Last-Modified: Wed Nov 11 14:10:00 PST 1998 >Originator: gregm@t3.com >Organization: >Release: 1.3.1 >Environment: Origin 200 IRIX64 nesn 6.4 02121744 IP27 gcc version egcs-2.90.29 980515 (egcs-1.0.3 release) >Description: The suggested workaround to problem 2606 (semctl(IPC_SET): Bad address at server startup) is to compile with -DUSE_FCNTL_SERIALIZED_ACCEPT. This fixes that problem but all ip entries in the access log are listed as 255.255.255.255 >How-To-Repeat: >Fix: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: randy State-Changed-When: Wed Nov 11 13:03:00 PST 1998 State-Changed-Why: This problem seems to be caused by compilation with gcc 2.8.1 and derivatives. Newer version of Apache now use FCNTL locking on this platform. From: Greg McGurk To: randy@apache.org Cc: apbugs@apache.org Subject: Re: os-irix/2829: wrong client ip address in access log Date: 11 Nov 1998 17:07:35 -0500 I believe the wrong ip address is caused by an inet_ntoa incompatibility between gcc and the Irix libraries. See http://reality.sgi.com/ariel/freeware/gcc-2.8.1-notes.html "Gcc does not correctly pass/return structures which are smaller than 16 bytes and which are not 8 bytes. The problem is very involved and difficult to fix. It affects a number of other targets also, but irix6 is affected the most, because it is a 64 bit target, and 4 byte structures are common. The exact problem is that structures are being padded at the wrong end, e.g. a 4 byte structure is loaded into the lower 4 bytes of the register when it should be loaded into the upper 4 bytes of the register." Gcc is consistent with itself, but not consistent with the SGI C compiler [and the SGI supplied runtime libraries], so the only failures that can happen are when there are library functions that take/return such structures. There are very few such library functions. I can only recall seeing a few of them: inet_ntoa, inet_aton, inet_lnaof, inet_netof, and semctl." randy@apache.org writes: > > [In order for any reply to be added to the PR database, ] > [you need to include in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > [If you do not include this Cc, your reply may be ig- ] > [nored unless you are responding to an explicit request ] > [from a developer. ] > [Reply only with text; DO NOT SEND ATTACHMENTS! ] > > > Synopsis: wrong client ip address in access log > > State-Changed-From-To: open-closed > State-Changed-By: randy > State-Changed-When: Wed Nov 11 13:03:00 PST 1998 > State-Changed-Why: > This problem seems to be caused by compilation with gcc 2.8.1 > and derivatives. Newer version of Apache now use FCNTL locking > on this platform. > >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]