From: Oleg Drokin <green@namesys.com>
To: Berjoza Roman <b_rom_s@4enet.by>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserfs+updatedb=oops
Date: Thu, 24 Jan 2002 13:29:44 +0300 [thread overview]
Message-ID: <20020124132944.A20375@namesys.com> (raw)
In-Reply-To: <20020123161944Z289790-13996+10616@vger.kernel.org>
In-Reply-To: <20020123161944Z289790-13996+10616@vger.kernel.org>
Hello!
On Wed, Jan 23, 2002 at 06:23:12PM +0200, Berjoza Roman wrote:
> Jan 23 12:56:40 ns1 kernel: EIP: 0010:[d_lookup+92/244] Not tainted
> Jan 23 12:56:40 ns1 kernel: Process kdeinit (pid: 3279, stackpage=c2fbf000)
> Jan 23 12:56:40 ns1 kernel: Call Trace: [cached_lookup+16/84]
> [link_path_walk+1184/1752] [getname+93/156] [path_walk+26/28]
> [__user_walk+53/80]
Hm. But there is no reiserfs code in the calltrace.
What I can say is that in d_lookup() this code falls:
tmp = tmp->next;
because tmp is NULL. (which means the our list is broken, right?)
I do not know how things went into this state, though.
Bye,
Oleg
next prev parent reply other threads:[~2002-01-24 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 16:23 reiserfs+updatedb=oops Berjoza Roman
2002-01-24 10:29 ` Oleg Drokin [this message]
[not found] ` <20020124105404.02895225988@angband.namesys.com>
2002-01-24 10:57 ` reiserfs+updatedb=oops Oleg Drokin
2002-01-24 20:38 ` reiserfs+updatedb=oops Andrew Morton
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=20020124132944.A20375@namesys.com \
--to=green@namesys.com \
--cc=b_rom_s@4enet.by \
--cc=linux-kernel@vger.kernel.org \
/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.