From: Mark Fortescue <mark@mtfhpc.demon.co.uk>
To: David Miller <davem@davemloft.net>
Cc: aaw@google.com, akpm@linux-foundation.org,
linux-arch@vger.kernel.org, sparclinux@vger.kernel.org,
wli@holomorphy.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [SPARC32] NULL pointer derefference
Date: Tue, 31 Jul 2007 06:35:29 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0707310557470.3926@mtfhpc.demon.co.uk> (raw)
In-Reply-To: <20070729.211929.78713482.davem@davemloft.net>
Hi David,
>
> One possible issue is sequencing, perhaps the stack argument copy
> is occuring before the new context is setup properly on sun4c.
>
I think it is somthing related to this but too much has changed for me to
work out what is going on. At present, I don't have a good enough
understanding of the virtual memory system and how it interracts with the
sun4c mmu.
The original code did a job lot of pte stuf in install_arg_page. The new
code seems to replace this using get_user_pages but I have not worked out
how get_user_pages gets to the point at which it allocated pte's i.e.
maps the stack memory it is about to put the arguments into.
> Another issue might be the new flush_cache_page() call in this
> new code in fs/exec.c, there are now cases where flush_cache_page()
> will be called on kernel addresses, and sun4c's implementation might
> not like that at all.
I commented out the flush_cache_page callmade in the new code. This had no
effect on the problem. Other tests have shown it is breaking earlier than
this.
I am going to try to narrow down exactly where the pointer gets messed up
as this should help.
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>
next prev parent reply other threads:[~2007-07-31 5:35 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 [this message]
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
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.0707310557470.3926@mtfhpc.demon.co.uk \
--to=mark@mtfhpc.demon.co.uk \
--cc=aaw@google.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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