From: James Cownie <jcownie@etnus.com>
To: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compaq Alpha: missing i-cache invalidates in ptrace (2.2.18, 2.4.0) ?
Date: Thu, 15 Feb 2001 13:32:55 +0000 [thread overview]
Message-ID: <14TOWl-51w-00@etnus.com> (raw)
In-Reply-To: Your message of "Thu, 15 Feb 2001 06:29:13 CST." <Pine.LNX.3.96.1010215062856.5873D-100000@mandrakesoft.mandrakesoft.com>
Jeff Garzik asked :-
> Does the same Alpha problem exist in 2.4.1-AC patches? (Alan Cox's
> patchkit)
It looks as if there's a very suitable fix in kernel/ptrace.c .
In access_one_page we have
if (write) {
maddr = kmap(page);
memcpy(maddr + (addr & ~PAGE_MASK), buf, len);
flush_page_to_ram(page);
flush_icache_page(vma, page);
kunmap(page);
}
which looks ideal to me...
That still leaves 2.2 broken, though :-(
-- Jim
James Cownie <jcownie@etnus.com>
Etnus, LLC. +44 117 9071438
http://www.etnus.com
next parent reply other threads:[~2001-02-15 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.1010215062856.5873D-100000@mandrakesoft.mandrakesoft.com>
2001-02-15 13:32 ` James Cownie [this message]
2001-02-15 12:23 Compaq Alpha: missing i-cache invalidates in ptrace (2.2.18, 2.4.0) ? James Cownie
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=14TOWl-51w-00@etnus.com \
--to=jcownie@etnus.com \
--cc=jgarzik@mandrakesoft.mandrakesoft.com \
--cc=linux-kernel@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