linux-kernel - Re: [PATCH -tip v8 11/26] kprobes: Allow probe on some kprobe functions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53314AEA.4040207@hitachi.com>
Date:	Tue, 25 Mar 2014 18:22:50 +0900
From:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Andi Kleen <andi@...stfloor.org>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	Sandeepa Prabhu <sandeepa.prabhu@...aro.org>,
	Frederic Weisbecker <fweisbec@...il.com>, x86@...nel.org,
	fche@...hat.com, mingo@...hat.com, systemtap@...rceware.org,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH -tip v8 11/26] kprobes: Allow probe on some kprobe functions

(2014/03/25 4:37), Steven Rostedt wrote:
> On Wed, 05 Mar 2014 21:00:00 +0900
> Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:
> 
>> There is no need to prohibit probing on the functions
>> used for preparation, registeration, optimization,
>> controll etc. Those are safely probed because those are
>> not invoked from breakpoint/fault/debug handlers,
>> there is no chance to cause recursive exceptions.
>>
>> Following functions are now removed from the kprobes blacklist.
>> add_new_kprobe
>> aggr_kprobe_disabled
>> alloc_aggr_kprobe
>> alloc_aggr_kprobe
>> arm_all_kprobes
>> __arm_kprobe
>> arm_kprobe
>> arm_kprobe_ftrace
>> check_kprobe_address_safe
>> collect_garbage_slots
>> collect_garbage_slots
>> collect_one_slot
>> debugfs_kprobe_init
>> __disable_kprobe
>> disable_kprobe
>> disarm_all_kprobes
>> __disarm_kprobe
>> disarm_kprobe
>> disarm_kprobe_ftrace
>> do_free_cleaned_kprobes
>> do_optimize_kprobes
>> do_unoptimize_kprobes
>> enable_kprobe
>> force_unoptimize_kprobe
>> free_aggr_kprobe
>> free_aggr_kprobe
>> __free_insn_slot
>> __get_insn_slot
>> get_optimized_kprobe
>> __get_valid_kprobe
>> init_aggr_kprobe
>> init_aggr_kprobe
>> in_nokprobe_functions
>> kick_kprobe_optimizer
>> kill_kprobe
>> kill_optimized_kprobe
>> kprobe_addr
>> kprobe_optimizer
>> kprobe_queued
>> kprobe_seq_next
>> kprobe_seq_start
>> kprobe_seq_stop
>> kprobes_module_callback
>> kprobes_open
>> optimize_all_kprobes
>> optimize_kprobe
>> prepare_kprobe
>> prepare_optimized_kprobe
>> register_aggr_kprobe
>> register_jprobe
>> register_jprobes
>> register_kprobe
>> register_kprobes
>> register_kretprobe
>> register_kretprobe
>> register_kretprobes
>> register_kretprobes
>> report_probe
>> show_kprobe_addr
>> try_to_optimize_kprobe
>> unoptimize_all_kprobes
>> unoptimize_kprobe
>> unregister_jprobe
>> unregister_jprobes
>> unregister_kprobe
>> __unregister_kprobe_bottom
>> unregister_kprobes
>> __unregister_kprobe_top
>> unregister_kretprobe
>> unregister_kretprobe
>> unregister_kretprobes
>> unregister_kretprobes
>> wait_for_kprobe_optimizer
>>
> 
> Did you test these like you did with the previous patch? What about the
> middle of these functions?

No, not yet tested in middle of those functions. Only the entries are
tested. OK, I'll do that.

Thank you,

-- 
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@...achi.com


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/