From: "Paweł Sikora" <pluto@pld-linux.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10rc3+cset == oops (fs).
Date: Sat, 11 Dec 2004 00:51:34 +0100 [thread overview]
Message-ID: <200412110051.35050.pluto@pld-linux.org> (raw)
In-Reply-To: <20041210152555.5c579892.akpm@osdl.org>
On Saturday 11 of December 2004 00:25, Andrew Morton wrote:
> Pawe__ Sikora <pluto@pld-linux.org> wrote:
> > I've just tried to boot the 2.6.10rc3+cset20041210_0507.
> >
> > [handcopy of the ooops]
> >
> > dereferencing null pointer
> > eip at: radix_tree_tag_clear
407:lib/radix-tree.c ****
408:lib/radix-tree.c **** if (*pathp->slot == NULL) <=== ooopses here
409:lib/radix-tree.c **** goto out;
410:lib/radix-tree.c ****
1341 .loc 1 408 0
1342 0605 8B45A4 movl -92(%ebp), %eax # <variable>.slot, D.9023
1343 0608 8B00 movl (%eax), %eax #* D.9023,
1344 060a 85C0 testl %eax, %eax #
1345 060c 744F je .L132 #,
> > trace:
> > (...)
> > test_clear_page_dirty
> > truncate_complete_page
> > truncate_inode_pages_range
> > truncate_inode_pages
> > generic_delete_inode
> > sys_unlink
> > initrd_load
> > prepare_namespace
> > (...)
>
> I can't think of any recent changes whish could cause something like this.
> Is this reproducible? If so, could you please work out which kernel
> version and bk snapshot introduced the bug? Thanks.
2.6.10rc1+cset20041025_0606 works fine (I'm using it now).
2.6.10rc3+cset20041210_0507 oopses.
I'll do more test later...
--
/* Copyright (C) 2003, SCO, Inc. This is valuable Intellectual Property. */
#define say(x) lie(x)
next prev parent reply other threads:[~2004-12-10 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 22:30 2.6.10rc3+cset == oops (fs) Paweł Sikora
2004-12-10 23:25 ` Andrew Morton
2004-12-10 23:51 ` Paweł Sikora [this message]
2004-12-11 8:36 ` Paweł Sikora
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=200412110051.35050.pluto@pld-linux.org \
--to=pluto@pld-linux.org \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox