From: Mark Fortescue <mark@mtfhpc.demon.co.uk>
To: Ollie Wild <aaw@google.com>
Cc: sparclinux@vger.kernel.org, wli@holomorphy.com,
linux-mm@kvack.org, davem@davemloft.net
Subject: Re: [SPARC32] NULL pointer derefference
Date: Tue, 31 Jul 2007 07:54:09 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0707310738240.4116@mtfhpc.demon.co.uk> (raw)
In-Reply-To: <65dd6fd50707302210y5b79a70di58eb2d46f3958025@mail.gmail.com>
>
> I feel like I ought to help out with this since it's my change which
> broke things, but I don't have access to a Sparc32 box. Does anyone
> have a remotely rebootable machine I can use?
>
> Ollie
>
sun4c Sparc32 are probably a bit thin on the ground. Im my experience,
they also have a habit of locking up (power up reset required) when
debugging kernel issues.
However, I think I am getting somewhere.
The problem would apear to be that sun4c_update_mmu_cache is beeing called
(either directly from the fault handling code or via update_mmu_cache)
before the mm->context has been set up. The only place I found that sets
this is sun4c_switch_mm (called from the scheduler as switch_mm).
In other words, the vma system is not operational untill after the task
gets scheduled.
There may be a way around this - by calling sun4c_alloc_context when the
mm gets set up. I will give it a go and see what happens.
David, are there any issues that you are aware of in calling
sun4c_alloc_context without switching to it?
Regards
Mark Fortescue.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-07-31 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 2:18 Mark Fortescue
2007-07-30 4:19 ` David Miller, Mark Fortescue
2007-07-30 10:39 ` Mark Fortescue
2007-07-31 5:35 ` Mark Fortescue
2007-07-31 6:42 ` David Miller, Mark Fortescue
2007-07-31 7:55 ` [PATCH] " Mark Fortescue
2007-07-31 9:02 ` David Miller, Mark Fortescue
2007-07-31 5:10 ` Ollie Wild
2007-07-31 6:54 ` Mark Fortescue [this message]
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=Pine.LNX.4.61.0707310738240.4116@mtfhpc.demon.co.uk \
--to=mark@mtfhpc.demon.co.uk \
--cc=aaw@google.com \
--cc=davem@davemloft.net \
--cc=linux-mm@kvack.org \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.com \
/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