This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue Apr 23 17:26:02 2024 Received: from entropy.muc.muohio.edu (IDENT:root@entropy.muc.muohio.edu [134.53.213.10]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id LAA18988 for ; Fri, 23 Jul 1999 11:54:09 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by entropy.muc.muohio.edu (8.8.7/8.8.7) with ESMTP id MAA12217; Fri, 23 Jul 1999 12:52:02 -0400 Received: by vger.rutgers.edu via listexpand id ; Fri, 23 Jul 1999 12:28:59 -0400 Received: by vger.rutgers.edu id ; Fri, 23 Jul 1999 12:25:13 -0400 Received: from 20717487209.ria.net ([207.174.87.209]:1110 "EHLO diamond.pangalactic.org") by vger.rutgers.edu with ESMTP id ; Fri, 23 Jul 1999 12:21:18 -0400 Received: from pangalactic.org (rob@localhost [127.0.0.1]) by diamond.pangalactic.org (8.8.7/8.8.7) with ESMTP id KAA02394 for ; Fri, 23 Jul 1999 10:22:14 -0600 Message-Id: <379896B6.FDE73FEB@pangalactic.org> Date: Fri, 23 Jul 1999 10:22:14 -0600 From: Rob Riggs X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10-ac12 i686) X-Accept-Language: en Mime-Version: 1.0 To: linux-kernel@vger.rutgers.edu Subject: processes stuck in skb_recv_datagram Content-Type: multipart/mixed; boundary="------------B11A0864564A79652B927111" Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig This is a multi-part message in MIME format. --------------B11A0864564A79652B927111 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Seems I munged the kernel list address on the first attempt to get this out... --------------B11A0864564A79652B927111 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <37974FFF.E5BFF9EA@pangalactic.org> Date: Thu, 22 Jul 1999 11:08:15 -0600 From: Rob Riggs X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10-ac12 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-kernel@vger.rutger.edu, linux-gcc@vger.rutgers.edu Subject: processes stuck in skb_recv_datagram Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This problem was previously mentioned: http://www.tux.org/hypermail/linux-kernel/1999week27/0326.html http://www.tux.org/hypermail/linux-kernel/1999week26/0796.html Multiple threads calling gethostbyname_r() (and using DNS to resolve) ends up with threads stuck in skb_recv_datagram. This occurs under kernels up to 2.3.10 and 2.2.10ac12 with glibc-2.1.1 and glibc-2.0.7. Under 2.0 kernels (including 2.0.37) it causes multiple oopses. Python and C code to illustrate this problem are available: ftp://ftp.pangalactic.org/pub/outgoing/pytest ftp://ftp.pangalactic.org/pub/outgoing/thrtest.c I've received only one comment on this problem. Alan Cox did suggest that the oops in 2.0 kernels had been fixed under 2.0.37, but it has not. I've posted this again to the kernel-list to note that the problem still occurs under the latest AC release. I've also directed it to the linux-gcc list since the problem under 2.2 and 2.3 may well be in glibc and not related to the kernel oopses under 2.0, as was my first impression. Any comments or suggestions will be greatly appreciated. -- Rob Riggs Technical Staff Tummy.com, Ltd. http://www.tummy.com/ --------------B11A0864564A79652B927111-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/