From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>, Will Deacon <will.deacon@arm.com>,
Jon Medhurst <tixy@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, David Long <dave.long@linaro.org>,
stable@vger.kernel.org
Subject: Re: [BUGFIX PATCH v3 0/4] arm: kprobes: Fix to prohibit probing on unsafe functions
Date: Tue, 8 May 2018 12:25:03 +0100 [thread overview]
Message-ID: <20180508112503.GD16141@n2100.armlinux.org.uk> (raw)
In-Reply-To: <152540727123.29650.13679359124038587629.stgit@devbox>
On Fri, May 04, 2018 at 01:14:31PM +0900, Masami Hiramatsu wrote:
> Hi,
>
> This is the 3rd version of bugfix series for kprobes on arm.
> This series fixes 4 different issues which I found.
>
> - Fix to use smp_processor_id() after disabling preemption.
> - Prohibit probing on optimized_callback() for avoiding
> recursive probe.
> - Prohibit kprobes on do_undefinstr() by same reason.
> - Prohibit kprobes on get_user() by same reason.
>
> >From v2, I included another 2 bugfixes (1/4 and 2/4)
> which are not merged yet, and added "Cc: stable@vger.kernel.org",
> since there are obvious bugs.
Please submit them to the patch system, thanks.
>
> Thanks,
>
> ---
>
> Masami Hiramatsu (4):
> arm: kprobes: Fix to use get_kprobe_ctlblk after irq-disabed
> arm: kprobes: Prohibit probing on optimized_callback
> arm: kprobes: Prohibit kprobes on do_undefinstr
> arm: kprobes: Prohibit kprobes on get_user functions
>
>
> arch/arm/include/asm/assembler.h | 10 ++++++++++
> arch/arm/kernel/traps.c | 5 ++++-
> arch/arm/lib/getuser.S | 10 ++++++++++
> arch/arm/probes/kprobes/opt-arm.c | 4 +++-
> 4 files changed, 27 insertions(+), 2 deletions(-)
>
> --
> Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
next prev parent reply other threads:[~2018-05-08 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 4:14 [BUGFIX PATCH v3 0/4] arm: kprobes: Fix to prohibit probing on unsafe functions Masami Hiramatsu
2018-05-04 4:15 ` [BUGFIX PATCH v3 1/4] arm: kprobes: Fix to use get_kprobe_ctlblk after irq-disabed Masami Hiramatsu
2018-05-04 4:15 ` [BUGFIX PATCH v3 2/4] arm: kprobes: Prohibit probing on optimized_callback Masami Hiramatsu
2018-05-04 4:15 ` [BUGFIX PATCH v3 3/4] arm: kprobes: Prohibit kprobes on do_undefinstr Masami Hiramatsu
2018-05-04 4:16 ` [BUGFIX PATCH v3 4/4] arm: kprobes: Prohibit kprobes on get_user functions Masami Hiramatsu
2018-05-08 11:25 ` Russell King - ARM Linux [this message]
2018-05-12 0:42 ` [BUGFIX PATCH v3 0/4] arm: kprobes: Fix to prohibit probing on unsafe functions Masami Hiramatsu
2018-05-12 4:31 ` Greg KH
2018-05-12 9:06 ` Russell King - ARM Linux
2018-05-12 11:31 ` Masami Hiramatsu
2018-05-12 17:29 ` Florian Fainelli
2018-05-13 1:55 ` Masami Hiramatsu
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=20180508112503.GD16141@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=dave.long@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tixy@linaro.org \
--cc=wangnan0@huawei.com \
--cc=will.deacon@arm.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