This is the mail archive of the mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: next test release (5th)

On Sun, Oct 01, 2000 at 01:38:43PM +0200, Thorsten Kukuk wrote:
> Hi,
> On Sat, Sep 30, Jakub Jelinek wrote:
> > On Fri, Sep 29, 2000 at 09:30:16AM +0200, Thorsten Kukuk wrote:
> > > 
> > > Hi,
> > > 
> > > I have only one bigger problem: H.J. Lu's patch for sunrpc/udp
> > > (IP_PKTINFO) patch does not seem to work on big endian platforms.
> > > 
> > > The server sends the data to the network, but the client never
> > > becomes the answer. I will try to look at it, but I don't know
> > > anything about IP_PKTINFO.
> > 
> > I think this is related to the portmap hang on boot. Older kernels used to
> > even crash when glibc 2.1.9x portmap was started, then DaveM fixed a bug in
> > the kernel and said something needs to be fixed in userland as well, but I
> > did not get to it yet and cannot find the mail right now (vger is not
> > accessible now and DaveM is until monday? on holidays).
> > So I guess 2.1.95 can be released with this known issue and I'll work with
> > DaveM on fixing sunrpc/udp on SPARC soon afterwards.
> Does this mean there is a bug in the SPARC code in all kernel versions
> with IP_PKTINFO ? Maybe this a problem with sparc64, but I doubt this
> is the reason for the sparc32 problems with HJLs patch.
> If I remove the patch from HJL, everything works fine on sparc32.
> Try the following: boot a sparc32 system with glibc 2.1.94 without
> HJLs patch. Then kill ypbind and restart it, but LD_PRELOAD glibc 2.1.94
> with the patch. Everything will work except ypbind. So I doubt that it
> is a problem with the kernel and portmap. I think the portmap problem
> you see comes from the problem with glibc.

I doubt my patch is the problem unless the aligment is an issue. It may
be a trigger for the real problem somewhere else. My patch doesn't even
touch the IP_PKTINFO information from the kernel. It just saves it and
sends it back with response. I don't how it can break anything. Have
you checked if all the aligments in my patch are ok for sparc32?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]