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, 18 Mar 2005 19:19:43 +0000 [thread overview]
Message-ID: <16955.10703.845656.684890@napali.hpl.hp.com> (raw)
In-Reply-To: <12404.1111129477@kao2.melbourne.sgi.com>
>>>>> On Fri, 18 Mar 2005 09:40:02 -0800, "Luck, Tony" <tony.luck@intel.com> said:
Tony> That reminds me ... someone asked why we don't have the same
Tony> test for lfetch a few lines further down in
Tony> ia64_do_page_fault() in the "no_context" case (we only test
Tony> for speculative access there).
Clearly a bug. Hopefully, that explains Keith's case as well?
--david
next prev parent reply other threads:[~2005-03-18 19:19 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 [this message]
2005-03-19 0:58 ` Luck, Tony
2005-03-22 3:04 ` Keith Owens
2005-03-25 1:17 ` David Mosberger
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=16955.10703.845656.684890@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