This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Thu Apr 25 02:55:47 2024 Received: from lml.valinux.com (postfix@lml.valinux.com [198.186.203.19]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id UAA01145 for ; Sat, 22 Jan 2000 20:03:51 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by lml.valinux.com (Postfix) with ESMTP id A38BF5B60F; Sat, 22 Jan 2000 02:03:03 -0800 (PST) Received: by vger.rutgers.edu via listexpand id ; Sat, 22 Jan 2000 01:52:33 -0500 Received: by vger.rutgers.edu id ; Fri, 21 Jan 2000 18:13:24 -0500 Received: from ns.mtu.ru ([195.34.32.10]:41814 "HELO mtu.ru") by vger.rutgers.edu with SMTP id ; Fri, 21 Jan 2000 15:50:52 -0500 Received: from idiom.com (dial57099.mtu-net.ru [195.34.57.99]) by mtu.ru (Postfix) with ESMTP id AE6722F13; Fri, 21 Jan 2000 23:50:38 +0300 (MSK) Message-Id: <3888C589.F344BDA1@idiom.com> Date: Fri, 21 Jan 2000 23:46:01 +0300 From: Hans Reiser X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686) X-Accept-Language: en, ru Mime-Version: 1.0 To: Willy Tarreau , "linux-kernel@vger.rutgers.edu" Cc: "Vladimir V. Saveliev" , "zag@zag.botik.ru" , "yura@namesys.botik.ru" , Chris Mason , Konstantin Imianitov , Alexander Z Subject: [Fwd: 2.2.14 oopses : is this a clue ?] Content-Type: multipart/mixed; boundary="------------BD5DE5C842506ACFE89FBFD5" X-Recipient: willy@novworld.Novecom.Fr 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. --------------BD5DE5C842506ACFE89FBFD5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks for being on top of this willy, it really helps us to get such detailed error analysis. Hans -- Get Linux (http://www.kernel.org) plus ReiserFS (http://devlinux.org/namesys). If you sell an OS or internet appliance, buy a port of ReiserFS! If you need customizations and industrial grade support, we sell them. --------------BD5DE5C842506ACFE89FBFD5 Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Content-Disposition: inline From vger.rutgers.edu!owner-linux-kernel-outgoing Thu Jan 20 23:08:52 2000 remote from botik Received: from idiom.com([216.240.32.1]) ident root by pier.botik.ru (Smail-3.2.0.98/botik-0.15 1999-Sep-9 #28) with esmtp for id m12BNsw-001O3qa; Thu, 20 Jan 2000 23:08:50 +0300 (MSK) Received: from nic.funet.fi (nic.funet.fi [193.166.0.145]) by idiom.com (8.9.3/8.9.3) with ESMTP id MAA88017; Thu, 20 Jan 2000 12:08:39 -0800 (PST) Received: from vger.rutgers.edu ([128.6.190.2]:31480 "EHLO vger.rutgers.edu" ident: "NO-IDENT-SERVICE[2]" smtp-auth: TLS-CIPHER: ) by nic.funet.fi with ESMTP id ; Thu, 20 Jan 2000 22:08:27 +0200 Received: by vger.rutgers.edu via listexpand id ; Thu, 20 Jan 2000 12:50:20 -0500 Received: by vger.rutgers.edu id ; Thu, 20 Jan 2000 11:37:48 -0500 Received: from web1104.mail.yahoo.com ([128.11.23.124]:2038 "HELO web1104.mail.yahoo.com") by vger.rutgers.edu with SMTP id ; Thu, 20 Jan 2000 11:17:16 -0500 Received: (qmail 8965 invoked by uid 60001); 20 Jan 2000 16:17:11 -0000 Message-ID: <20000120161711.8964.qmail@web1104.mail.yahoo.com> Received: from [195.6.58.78] by web1104.mail.yahoo.com; Thu, 20 Jan 2000 17:17:10 CET Date: Thu, 20 Jan 2000 17:17:10 +0100 (CET) From: =?iso-8859-1?q?willy=20tarreau?= Subject: 2.2.14 oopses : is this a clue ? To: linux-kernel@vger.rutgers.edu MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig X-Mozilla-Status2: 00000000 Hi all, I had an oops yesterday in ext2_check_dir_entry() (fs/ext2/dir.c). Although I couldn't grab the messages, I'm pretty sure it's because the dir_entry pointer (de) was NULL. Why do I think about this, would you say ? Simply because of exactly same a problem I reported two weeks ago to the reiserfs developpers, in which case it was really "de" which was NULL. I inserted a test on "de" in this function, and no more crash, but no message either, so no possible conclusion on this... I must say that it occured on a bad disk with lots of hardware errors, and I don't use this disk anymore, but do use reiserfs on my notebook without an error. In the two last oops reports in LKML, the dir_entry is involved ... in doubt, I've added a check on "de" at the very beginning of ext2_check_dir_entry, and I'm waiting for the crash to appear again, or at least a message. Is there a reason for which all these functions to be called with a NULL dir_entry ? I'm wondering about using IKD for this, but I don't know if I could insert break points in the source code, sort of "asserts" which force it to take the control in case of a condition match. Eg: if (de == NULL) raise_ikd(); Perhaps something such as *(int *)NULL=0 ? Willy ___________________________________________________________ Do You Yahoo!? Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr - 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/ --------------BD5DE5C842506ACFE89FBFD5-- - 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/