From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 2.6.11] __copy_user breaks on unaligned src
Date: Fri, 25 Mar 2005 01:17:49 +0000 [thread overview]
Message-ID: <16963.26301.383089.505308@napali.hpl.hp.com> (raw)
In-Reply-To: <12404.1111129477@kao2.melbourne.sgi.com>
>>>>> On Tue, 22 Mar 2005 14:04:55 +1100, Keith Owens <kaos@sgi.com> said:
>> I don't see off-hand why this wouldn't work as intended.
Keith> It's got me puzzled as well. On my test system, single
Keith> stepping the offending instruction _WILL_ cause a fault, but
Keith> letting it run normally does not cause an error. A normal
Keith> run (without single step) definitely uses lfetch with an
Keith> invalid address, however ia64_fault() is not invoked, not
Keith> even for isr.na.
Keith> I am trying to get some time on the big system to reproduce
Keith> the problem and see why lfetch is faulting there. Is there
Keith> any chance that a concurrent interrupt (the failing system
Keith> does a lot of I/O) can lose the lfetch status?
Hmmh, odd indeed. I changed prefetch()/prefetchw() to use
lfetch.fault and now the kernel dies early on on an lfetch.fault that
goes to address 0 (triggered by find_pid()). Since that's a NaT page,
you'd expect a general exception (NaT consumption). However, the CPU
seems to get stuck in an infinite loop of general exceptions. From
what I can tell, it get to "dispatch_to_fault_handler" and as soon as
it re-enables PSR.IC or perhaps PSR.I (not sure which), it gets
another general exception fault.
--david
next prev parent reply other threads:[~2005-03-25 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 7:04 [patch 2.6.11] __copy_user breaks on unaligned src Keith Owens
2005-03-18 7:17 ` David Mosberger
2005-03-18 17:40 ` Luck, Tony
2005-03-18 19:19 ` David Mosberger
2005-03-19 0:58 ` Luck, Tony
2005-03-22 3:04 ` Keith Owens
2005-03-25 1:17 ` David Mosberger [this message]
2005-03-25 7:59 ` David Mosberger
2005-03-25 20:27 ` David Mosberger
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=16963.26301.383089.505308@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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