* [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context
@ 2018-05-02 0:02 Song Liu
2018-05-02 0:02 ` [PATCH bpf-next 2/2] bpf: add selftest for stackmap with build_id in NMI context Song Liu
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Song Liu @ 2018-05-02 0:02 UTC (permalink / raw)
To: netdev
Cc: Song Liu, kernel-team, Alexei Starovoitov, Daniel Borkmann,
Peter Zijlstra
Currently, we cannot parse build_id in nmi context because of
up_read(¤t->mm->mmap_sem), this makes stackmap with build_id
less useful. This patch enables parsing build_id in nmi by putting
the up_read() call in irq_work. To avoid memory allocation in nmi
context, we use per cpu variable for the irq_work. As a result, only
one irq_work per cpu is allowed. If the irq_work is in-use, we
fallback to only report ips.
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Song Liu <songliubraving@fb.com>
---
kernel/bpf/stackmap.c | 60 +++++++++++++++++++++++++++++++++++++++++++++------
1 file changed, 54 insertions(+), 6 deletions(-)
diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
index 3ba102b..c33fec1 100644
--- a/kernel/bpf/stackmap.c
+++ b/kernel/bpf/stackmap.c
@@ -11,6 +11,7 @@
#include <linux/perf_event.h>
#include <linux/elf.h>
#include <linux/pagemap.h>
+#include <linux/irq_work.h>
#include "percpu_freelist.h"
#define STACK_CREATE_FLAG_MASK \
@@ -32,6 +33,23 @@ struct bpf_stack_map {
struct stack_map_bucket *buckets[];
};
+/* irq_work to run up_read() for build_id lookup in nmi context */
+struct stack_map_irq_work {
+ struct irq_work work;
+ struct rw_semaphore *sem;
+};
+
+static void up_read_work(struct irq_work *entry)
+{
+ struct stack_map_irq_work *work = container_of(entry,
+ struct stack_map_irq_work, work);
+
+ up_read(work->sem);
+ work->sem = NULL;
+}
+
+DEFINE_PER_CPU(struct stack_map_irq_work, irq_work);
+
static inline bool stack_map_use_build_id(struct bpf_map *map)
{
return (map->map_flags & BPF_F_STACK_BUILD_ID);
@@ -267,17 +285,27 @@ static void stack_map_get_build_id_offset(struct bpf_stack_build_id *id_offs,
{
int i;
struct vm_area_struct *vma;
+ bool in_nmi_ctx = in_nmi();
+ bool irq_work_busy = false;
+ struct stack_map_irq_work *work;
+
+ if (in_nmi_ctx) {
+ work = this_cpu_ptr(&irq_work);
+ if (work->sem)
+ /* cannot queue more up_read, fallback */
+ irq_work_busy = true;
+ }
/*
- * We cannot do up_read() in nmi context, so build_id lookup is
- * only supported for non-nmi events. If at some point, it is
- * possible to run find_vma() without taking the semaphore, we
- * would like to allow build_id lookup in nmi context.
+ * We cannot do up_read() in nmi context. To do build_id lookup
+ * in nmi context, we need to run up_read() in irq_work. We use
+ * a percpu variable to do the irq_work. If the irq_work is
+ * already used by another lookup, we fall back to report ips.
*
* Same fallback is used for kernel stack (!user) on a stackmap
* with build_id.
*/
- if (!user || !current || !current->mm || in_nmi() ||
+ if (!user || !current || !current->mm || irq_work_busy ||
down_read_trylock(¤t->mm->mmap_sem) == 0) {
/* cannot access current->mm, fall back to ips */
for (i = 0; i < trace_nr; i++) {
@@ -299,7 +327,13 @@ static void stack_map_get_build_id_offset(struct bpf_stack_build_id *id_offs,
- vma->vm_start;
id_offs[i].status = BPF_STACK_BUILD_ID_VALID;
}
- up_read(¤t->mm->mmap_sem);
+
+ if (!in_nmi_ctx)
+ up_read(¤t->mm->mmap_sem);
+ else {
+ work->sem = ¤t->mm->mmap_sem;
+ irq_work_queue(&work->work);
+ }
}
BPF_CALL_3(bpf_get_stackid, struct pt_regs *, regs, struct bpf_map *, map,
@@ -575,3 +609,17 @@ const struct bpf_map_ops stack_map_ops = {
.map_update_elem = stack_map_update_elem,
.map_delete_elem = stack_map_delete_elem,
};
+
+static int __init stack_map_init(void)
+{
+ int cpu;
+ struct stack_map_irq_work *work;
+
+ for_each_possible_cpu(cpu) {
+ work = per_cpu_ptr(&irq_work, cpu);
+ init_irq_work(&work->work, up_read_work);
+ }
+ pr_info("%s: done\n", __func__);
+ return 0;
+}
+subsys_initcall(stack_map_init);
--
2.9.5
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH bpf-next 2/2] bpf: add selftest for stackmap with build_id in NMI context 2018-05-02 0:02 [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Song Liu @ 2018-05-02 0:02 ` Song Liu 2018-05-02 3:34 ` [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context kbuild test robot ` (2 subsequent siblings) 3 siblings, 0 replies; 8+ messages in thread From: Song Liu @ 2018-05-02 0:02 UTC (permalink / raw) To: netdev; +Cc: Song Liu, kernel-team This new test captures stackmap with build_id with hardware event PERF_COUNT_HW_CPU_CYCLES. Because we only support one ips-to-build_id lookup per cpu in NMI context, stack_amap will not be able to do the lookup in this test. Therefore, we didn't do compare_stack_ips(), as it will alwasy fail. urandom_read.c is extended to run configurable cycles so that it can be caught by the perf event. Signed-off-by: Song Liu <songliubraving@fb.com> --- tools/testing/selftests/bpf/test_progs.c | 137 +++++++++++++++++++++++++++++ tools/testing/selftests/bpf/urandom_read.c | 10 ++- 2 files changed, 145 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/bpf/test_progs.c b/tools/testing/selftests/bpf/test_progs.c index aa336f0..00bb08c 100644 --- a/tools/testing/selftests/bpf/test_progs.c +++ b/tools/testing/selftests/bpf/test_progs.c @@ -1272,6 +1272,142 @@ static void test_stacktrace_build_id(void) return; } +static void test_stacktrace_build_id_nmi(void) +{ + int control_map_fd, stackid_hmap_fd, stackmap_fd, stack_amap_fd; + const char *file = "./test_stacktrace_build_id.o"; + int err, pmu_fd, prog_fd; + struct perf_event_attr attr = { + .sample_freq = 5000, + .freq = 1, + .type = PERF_TYPE_HARDWARE, + .config = PERF_COUNT_HW_CPU_CYCLES, + }; + __u32 key, previous_key, val, duration = 0; + struct bpf_object *obj; + char buf[256]; + int i, j; + struct bpf_stack_build_id id_offs[PERF_MAX_STACK_DEPTH]; + int build_id_matches = 0; + + err = bpf_prog_load(file, BPF_PROG_TYPE_PERF_EVENT, &obj, &prog_fd); + if (CHECK(err, "prog_load", "err %d errno %d\n", err, errno)) + goto out; + + pmu_fd = syscall(__NR_perf_event_open, &attr, -1 /* pid */, + 0 /* cpu 0 */, -1 /* group id */, + 0 /* flags */); + if (CHECK(pmu_fd < 0, "perf_event_open", + "err %d errno %d. Does the test host support PERF_COUNT_HW_CPU_CYCLES?\n", + pmu_fd, errno)) + goto close_prog; + + err = ioctl(pmu_fd, PERF_EVENT_IOC_ENABLE, 0); + if (CHECK(err, "perf_event_ioc_enable", "err %d errno %d\n", + err, errno)) + goto close_pmu; + + err = ioctl(pmu_fd, PERF_EVENT_IOC_SET_BPF, prog_fd); + if (CHECK(err, "perf_event_ioc_set_bpf", "err %d errno %d\n", + err, errno)) + goto disable_pmu; + + /* find map fds */ + control_map_fd = bpf_find_map(__func__, obj, "control_map"); + if (CHECK(control_map_fd < 0, "bpf_find_map control_map", + "err %d errno %d\n", err, errno)) + goto disable_pmu; + + stackid_hmap_fd = bpf_find_map(__func__, obj, "stackid_hmap"); + if (CHECK(stackid_hmap_fd < 0, "bpf_find_map stackid_hmap", + "err %d errno %d\n", err, errno)) + goto disable_pmu; + + stackmap_fd = bpf_find_map(__func__, obj, "stackmap"); + if (CHECK(stackmap_fd < 0, "bpf_find_map stackmap", "err %d errno %d\n", + err, errno)) + goto disable_pmu; + + stack_amap_fd = bpf_find_map(__func__, obj, "stack_amap"); + if (CHECK(stack_amap_fd < 0, "bpf_find_map stack_amap", + "err %d errno %d\n", err, errno)) + goto disable_pmu; + + assert(system("dd if=/dev/urandom of=/dev/zero count=4 2> /dev/null") + == 0); + assert(system("taskset 0x1 ./urandom_read 100000") == 0); + /* disable stack trace collection */ + key = 0; + val = 1; + bpf_map_update_elem(control_map_fd, &key, &val, 0); + + /* for every element in stackid_hmap, we can find a corresponding one + * in stackmap, and vise versa. + */ + err = compare_map_keys(stackid_hmap_fd, stackmap_fd); + if (CHECK(err, "compare_map_keys stackid_hmap vs. stackmap", + "err %d errno %d\n", err, errno)) + goto disable_pmu; + + err = compare_map_keys(stackmap_fd, stackid_hmap_fd); + if (CHECK(err, "compare_map_keys stackmap vs. stackid_hmap", + "err %d errno %d\n", err, errno)) + goto disable_pmu; + + err = extract_build_id(buf, 256); + + if (CHECK(err, "get build_id with readelf", + "err %d errno %d\n", err, errno)) + goto disable_pmu; + + err = bpf_map_get_next_key(stackmap_fd, NULL, &key); + if (CHECK(err, "get_next_key from stackmap", + "err %d, errno %d\n", err, errno)) + goto disable_pmu; + + do { + char build_id[64]; + + err = bpf_map_lookup_elem(stackmap_fd, &key, id_offs); + if (CHECK(err, "lookup_elem from stackmap", + "err %d, errno %d\n", err, errno)) + goto disable_pmu; + for (i = 0; i < PERF_MAX_STACK_DEPTH; ++i) + if (id_offs[i].status == BPF_STACK_BUILD_ID_VALID && + id_offs[i].offset != 0) { + for (j = 0; j < 20; ++j) + sprintf(build_id + 2 * j, "%02x", + id_offs[i].build_id[j] & 0xff); + if (strstr(buf, build_id) != NULL) + build_id_matches = 1; + } + previous_key = key; + } while (bpf_map_get_next_key(stackmap_fd, &previous_key, &key) == 0); + + if (CHECK(build_id_matches < 1, "build id match", + "Didn't find expected build ID from the map\n")) + goto disable_pmu; + + /* + * We intentionally skip compare_stack_ips(). This is because we + * only support one in_nmi() ips-to-build_id translation per cpu + * at any time, thus stack_amap here will always fallback to + * BPF_STACK_BUILD_ID_IP; + */ + +disable_pmu: + ioctl(pmu_fd, PERF_EVENT_IOC_DISABLE); + +close_pmu: + close(pmu_fd); + +close_prog: + bpf_object__close(obj); + +out: + return; +} + #define MAX_CNT_RAWTP 10ull #define MAX_STACK_RAWTP 100 struct get_stack_trace_t { @@ -1425,6 +1561,7 @@ int main(void) test_tp_attach_query(); test_stacktrace_map(); test_stacktrace_build_id(); + test_stacktrace_build_id_nmi(); test_stacktrace_map_raw_tp(); test_get_stack_raw_tp(); diff --git a/tools/testing/selftests/bpf/urandom_read.c b/tools/testing/selftests/bpf/urandom_read.c index 4acfdeb..9de8b7c 100644 --- a/tools/testing/selftests/bpf/urandom_read.c +++ b/tools/testing/selftests/bpf/urandom_read.c @@ -6,15 +6,21 @@ #include <stdlib.h> #define BUF_SIZE 256 -int main(void) + +int main(int argc, char *argv[]) { int fd = open("/dev/urandom", O_RDONLY); int i; char buf[BUF_SIZE]; + int count = 4; if (fd < 0) return 1; - for (i = 0; i < 4; ++i) + + if (argc == 2) + count = atoi(argv[1]); + + for (i = 0; i < count; ++i) read(fd, buf, BUF_SIZE); close(fd); -- 2.9.5 ^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context 2018-05-02 0:02 [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Song Liu 2018-05-02 0:02 ` [PATCH bpf-next 2/2] bpf: add selftest for stackmap with build_id in NMI context Song Liu @ 2018-05-02 3:34 ` kbuild test robot 2018-05-02 3:34 ` [RFC PATCH] bpf: __pcpu_scope_irq_work can be static kbuild test robot 2018-05-02 9:21 ` [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Peter Zijlstra 3 siblings, 0 replies; 8+ messages in thread From: kbuild test robot @ 2018-05-02 3:34 UTC (permalink / raw) To: Song Liu Cc: kbuild-all, netdev, Song Liu, kernel-team, Alexei Starovoitov, Daniel Borkmann, Peter Zijlstra Hi Song, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on bpf-next/master] url: https://github.com/0day-ci/linux/commits/Song-Liu/bpf-enable-stackmap-with-build_id-in-nmi-context/20180502-081727 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) >> kernel/bpf/stackmap.c:51:1: sparse: symbol '__pcpu_scope_irq_work' was not declared. Should it be static? Please review and possibly fold the followup patch. --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation ^ permalink raw reply [flat|nested] 8+ messages in thread
* [RFC PATCH] bpf: __pcpu_scope_irq_work can be static 2018-05-02 0:02 [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Song Liu 2018-05-02 0:02 ` [PATCH bpf-next 2/2] bpf: add selftest for stackmap with build_id in NMI context Song Liu 2018-05-02 3:34 ` [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context kbuild test robot @ 2018-05-02 3:34 ` kbuild test robot 2018-05-02 9:21 ` [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Peter Zijlstra 3 siblings, 0 replies; 8+ messages in thread From: kbuild test robot @ 2018-05-02 3:34 UTC (permalink / raw) To: Song Liu Cc: kbuild-all, netdev, Song Liu, kernel-team, Alexei Starovoitov, Daniel Borkmann, Peter Zijlstra Fixes: 1bd02fb7c12e ("bpf: enable stackmap with build_id in nmi context") Signed-off-by: Fengguang Wu <fengguang.wu@intel.com> --- stackmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c index c33fec1..5d0a951 100644 --- a/kernel/bpf/stackmap.c +++ b/kernel/bpf/stackmap.c @@ -48,7 +48,7 @@ static void up_read_work(struct irq_work *entry) work->sem = NULL; } -DEFINE_PER_CPU(struct stack_map_irq_work, irq_work); +static DEFINE_PER_CPU(struct stack_map_irq_work, irq_work); static inline bool stack_map_use_build_id(struct bpf_map *map) { ^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context 2018-05-02 0:02 [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Song Liu ` (2 preceding siblings ...) 2018-05-02 3:34 ` [RFC PATCH] bpf: __pcpu_scope_irq_work can be static kbuild test robot @ 2018-05-02 9:21 ` Peter Zijlstra 2018-05-02 16:48 ` Song Liu 3 siblings, 1 reply; 8+ messages in thread From: Peter Zijlstra @ 2018-05-02 9:21 UTC (permalink / raw) To: Song Liu; +Cc: netdev, kernel-team, Alexei Starovoitov, Daniel Borkmann On Tue, May 01, 2018 at 05:02:19PM -0700, Song Liu wrote: > @@ -267,17 +285,27 @@ static void stack_map_get_build_id_offset(struct bpf_stack_build_id *id_offs, > { > int i; > struct vm_area_struct *vma; > + bool in_nmi_ctx = in_nmi(); > + bool irq_work_busy = false; > + struct stack_map_irq_work *work; > + > + if (in_nmi_ctx) { > + work = this_cpu_ptr(&irq_work); > + if (work->sem) > + /* cannot queue more up_read, fallback */ > + irq_work_busy = true; > + } > > /* > + * We cannot do up_read() in nmi context. To do build_id lookup > + * in nmi context, we need to run up_read() in irq_work. We use > + * a percpu variable to do the irq_work. If the irq_work is > + * already used by another lookup, we fall back to report ips. > * > * Same fallback is used for kernel stack (!user) on a stackmap > * with build_id. > */ > + if (!user || !current || !current->mm || irq_work_busy || > down_read_trylock(¤t->mm->mmap_sem) == 0) { > /* cannot access current->mm, fall back to ips */ > for (i = 0; i < trace_nr; i++) { > @@ -299,7 +327,13 @@ static void stack_map_get_build_id_offset(struct bpf_stack_build_id *id_offs, > - vma->vm_start; > id_offs[i].status = BPF_STACK_BUILD_ID_VALID; > } > + > + if (!in_nmi_ctx) > + up_read(¤t->mm->mmap_sem); > + else { > + work->sem = ¤t->mm->mmap_sem; > + irq_work_queue(&work->work); > + } > } This is disguisting.. :-) It's broken though, I've bet you've never actually ran this with lockdep enabled for example. Also, you set work->sem before you do trylock, if the trylock fails you return early and keep work->sem set, which will thereafter always result in irq_work_busy. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context 2018-05-02 9:21 ` [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Peter Zijlstra @ 2018-05-02 16:48 ` Song Liu 2018-05-02 17:30 ` Peter Zijlstra 0 siblings, 1 reply; 8+ messages in thread From: Song Liu @ 2018-05-02 16:48 UTC (permalink / raw) To: Peter Zijlstra Cc: Networking, Kernel Team, Alexei Starovoitov, Daniel Borkmann > On May 2, 2018, at 2:21 AM, Peter Zijlstra <peterz@infradead.org> wrote: > > On Tue, May 01, 2018 at 05:02:19PM -0700, Song Liu wrote: >> @@ -267,17 +285,27 @@ static void stack_map_get_build_id_offset(struct bpf_stack_build_id *id_offs, >> { >> int i; >> struct vm_area_struct *vma; >> + bool in_nmi_ctx = in_nmi(); >> + bool irq_work_busy = false; >> + struct stack_map_irq_work *work; >> + >> + if (in_nmi_ctx) { >> + work = this_cpu_ptr(&irq_work); >> + if (work->sem) >> + /* cannot queue more up_read, fallback */ >> + irq_work_busy = true; >> + } >> >> /* >> + * We cannot do up_read() in nmi context. To do build_id lookup >> + * in nmi context, we need to run up_read() in irq_work. We use >> + * a percpu variable to do the irq_work. If the irq_work is >> + * already used by another lookup, we fall back to report ips. >> * >> * Same fallback is used for kernel stack (!user) on a stackmap >> * with build_id. >> */ >> + if (!user || !current || !current->mm || irq_work_busy || >> down_read_trylock(¤t->mm->mmap_sem) == 0) { >> /* cannot access current->mm, fall back to ips */ >> for (i = 0; i < trace_nr; i++) { >> @@ -299,7 +327,13 @@ static void stack_map_get_build_id_offset(struct bpf_stack_build_id *id_offs, >> - vma->vm_start; >> id_offs[i].status = BPF_STACK_BUILD_ID_VALID; >> } >> + >> + if (!in_nmi_ctx) >> + up_read(¤t->mm->mmap_sem); >> + else { >> + work->sem = ¤t->mm->mmap_sem; >> + irq_work_queue(&work->work); >> + } >> } > > This is disguisting.. :-) > > It's broken though, I've bet you've never actually ran this with lockdep > enabled for example. I am not following here. I just run the new selftest with CONFIG_LOCKDEP on, and got no warning for this. > Also, you set work->sem before you do trylock, if the trylock fails you > return early and keep work->sem set, which will thereafter always result > in irq_work_busy. work->sem was set after down_read_trylock(). I guess you misread the patch? Thanks, Song ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context 2018-05-02 16:48 ` Song Liu @ 2018-05-02 17:30 ` Peter Zijlstra 2018-05-02 17:57 ` Song Liu 0 siblings, 1 reply; 8+ messages in thread From: Peter Zijlstra @ 2018-05-02 17:30 UTC (permalink / raw) To: Song Liu; +Cc: Networking, Kernel Team, Alexei Starovoitov, Daniel Borkmann On Wed, May 02, 2018 at 04:48:32PM +0000, Song Liu wrote: > > It's broken though, I've bet you've never actually ran this with lockdep > > enabled for example. > > I am not following here. I just run the new selftest with CONFIG_LOCKDEP on, > and got no warning for this. Weird, I would be expecting complaints about releasing an unheld lock. nmi_enter(),nmi_exit() have lockdep_off(),lockdep_on() resp. Which means that the down_trylock() will not be recorded. The up, which is done from IRQ context, will not be so supressed and should hit print_unlock_imbalance_bug(). > > Also, you set work->sem before you do trylock, if the trylock fails you > > return early and keep work->sem set, which will thereafter always result > > in irq_work_busy. > > work->sem was set after down_read_trylock(). I guess you misread the patch? Argh, yes indeed. Sorry. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context 2018-05-02 17:30 ` Peter Zijlstra @ 2018-05-02 17:57 ` Song Liu 0 siblings, 0 replies; 8+ messages in thread From: Song Liu @ 2018-05-02 17:57 UTC (permalink / raw) To: Peter Zijlstra Cc: Networking, Kernel Team, Alexei Starovoitov, Daniel Borkmann > On May 2, 2018, at 10:30 AM, Peter Zijlstra <peterz@infradead.org> wrote: > > On Wed, May 02, 2018 at 04:48:32PM +0000, Song Liu wrote: >>> It's broken though, I've bet you've never actually ran this with lockdep >>> enabled for example. >> >> I am not following here. I just run the new selftest with CONFIG_LOCKDEP on, >> and got no warning for this. > > Weird, I would be expecting complaints about releasing an unheld lock. > > nmi_enter(),nmi_exit() have lockdep_off(),lockdep_on() resp. Which means > that the down_trylock() will not be recorded. The up, which is done from > IRQ context, will not be so supressed and should hit > print_unlock_imbalance_bug(). > I am still not sure whether I am following. I guess your concern apply to spinlock only? lock_acquire() has the following in the beginning: if (unlikely(current->lockdep_recursion)) return; So it will not run in nmi context? On the other hand, semaphore and rw_semaphore should be ok in such cases? Thanks, Song ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2018-05-02 17:58 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2018-05-02 0:02 [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Song Liu 2018-05-02 0:02 ` [PATCH bpf-next 2/2] bpf: add selftest for stackmap with build_id in NMI context Song Liu 2018-05-02 3:34 ` [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context kbuild test robot 2018-05-02 3:34 ` [RFC PATCH] bpf: __pcpu_scope_irq_work can be static kbuild test robot 2018-05-02 9:21 ` [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Peter Zijlstra 2018-05-02 16:48 ` Song Liu 2018-05-02 17:30 ` Peter Zijlstra 2018-05-02 17:57 ` Song Liu
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox