From: oleg@redhat.com (Oleg Nesterov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] ARM: uprobes need icache flush after xol write
Date: Sun, 27 Apr 2014 14:21:51 +0200 [thread overview]
Message-ID: <20140427122151.GA19545@redhat.com> (raw)
In-Reply-To: <1398494096-11311-2-git-send-email-victor.kamensky@linaro.org>
On 04/25, Victor Kamensky wrote:
>
> Note ARM cache flush function need kernel address
> through which instruction write happened, so instead
> of using uprobes copy_to_page function changed
> code to explicitly map page and do memcpy.
Again, I can't review the changes in arm/, although I think there are
correct.
But personally I agree with this patch, we need something for v3.15,
and unless Russell objects I'd vote for this change.
FWIW,
Acked-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2014-04-27 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 6:34 [PATCH v5] ARM: uprobes need icache flush after xol write Victor Kamensky
2014-04-26 6:34 ` Victor Kamensky
2014-04-27 12:21 ` Oleg Nesterov [this message]
2014-04-27 21:01 ` David Long
2014-04-29 3:29 ` Victor Kamensky
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=20140427122151.GA19545@redhat.com \
--to=oleg@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).