From: Andrew Morton <akpm@osdl.org>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.9-rc1-bk14 Oops] In groups_search()
Date: Fri, 10 Sep 2004 00:49:35 -0700 [thread overview]
Message-ID: <20040910004935.15ee7b10.akpm@osdl.org> (raw)
In-Reply-To: <41415B15.1050402@bigpond.net.au>
Peter Williams <pwil3058@bigpond.net.au> wrote:
>
> > It would be useful if you could experiment with CONFIG_DEBUG_SLAB and
> > CONFIG_DEBUG_PAGEALLOC.
>
> With both of those enabled and all four patches applied the oops and the
> scheduling while atomic have stopped BUT I'm now getting 4 identical
> oops in kfree which seem to be associated with a segment fault in mount
> while my start up script is mounting some iso files with loopback.
gack. One bug at a time, OK?
Please drop those four patches - that idea didn't work out.
So we know that enabling CONFIG_DEBUG_SLAB and/or CONFIG_DEBUG_PAGEALLOC
makes the in_group_p() crash go away, yes?
Running out of ideas here. If you could, please try enabling those debug
options separately, see if that tells us something.
next prev parent reply other threads:[~2004-09-10 7:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 0:54 [2.6.9-rc1-bk14 Oops] In groups_search() Peter Williams
2004-09-09 8:06 ` Andrew Morton
2004-09-09 23:58 ` Peter Williams
2004-09-10 0:14 ` Andrew Morton
2004-09-10 1:53 ` Peter Williams
2004-09-10 3:06 ` Andrew Morton
2004-09-10 5:45 ` Peter Williams
2004-09-10 6:18 ` Andrew Morton
2004-09-10 6:28 ` Peter Williams
2004-09-10 6:37 ` Tim Hockin
2004-09-10 7:05 ` Peter Williams
2004-09-10 6:52 ` Andrew Morton
2004-09-10 7:43 ` Peter Williams
2004-09-10 7:49 ` Andrew Morton [this message]
2004-09-10 7:54 ` Andrew Morton
2004-09-10 8:13 ` Peter Williams
2004-09-10 8:46 ` Peter Williams
2004-09-10 8:54 ` Andrew Morton
2004-09-10 10:55 ` Peter Williams
2004-09-10 13:04 ` Peter Williams
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=20040910004935.15ee7b10.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pwil3058@bigpond.net.au \
/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.