search for: init_kprob

...ons((unsigned long) p->addr) || + within_kprobe_blacklist((unsigned long) p->addr) || jump_label_text_reserved(p->addr, p->addr)) { ret = -EINVAL; goto out; @@ -2065,14 +2054,41 @@ static struct notifier_block kprobe_module_nb = { .priority = 0 }; -static int __init init_kprobes(void) +/* + * Lookup and populate the kprobe_blacklist. + * + * Unlike the kretprobe blacklist, we'll need to determine + * the range of addresses that belong to the said functions, + * since a kprobe need not necessarily be at the beginning + * of a function. + */ +static void __init populat...

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. At this moment, I

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. At this moment, I

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

...t (disabled) [ 37.861176] type=2000 audit(1289932836.618:1): initialized [ 37.866706] initcall audit_init+0x0/0x10a returned 0 after 10749 usecs [ 37.873291] calling audit_tree_init+0x0/0x37 @ 1 [ 37.878059] initcall audit_tree_init+0x0/0x37 returned 0 after 0 usecs [ 37.884644] calling init_kprobes+0x0/0x13b @ 1 [ 37.891827] initcall init_kprobes+0x0/0x13b returned 0 after 2527 usecs [ 37.898344] calling hung_task_init+0x0/0x3c @ 1 [ 37.903111] initcall hung_task_init+0x0/0x3c returned 0 after 81 usecs [ 37.909611] calling utsname_sysctl_init+0x0/0xd @ 1 [ 37.914652] initcall ut...

Lots of changes since v2, too much to remember or summarize. Please ignore patch 11/11, it's just for my testing. Rich.

...d 0 after 276 usecs [ 27.207867] calling audit_watch_init+0x0/0x3a @ 1 [ 27.207993] initcall audit_watch_init+0x0/0x3a returned 0 after 1 usecs [ 27.208125] calling audit_tree_init+0x0/0x49 @ 1 [ 27.208278] initcall audit_tree_init+0x0/0x49 returned 0 after 1 usecs [ 27.208416] calling init_kprobes+0x0/0x16c @ 1 [ 27.239099] initcall init_kprobes+0x0/0x16c returned 0 after 29839 usecs [ 27.239238] calling hung_task_init+0x0/0x56 @ 1 [ 27.239589] initcall hung_task_init+0x0/0x56 returned 0 after 203 usecs [ 27.239729] calling irq_pm_init_ops+0x0/0x14 @ 1 [ 27.239855] initcall irq...