Skip to contentSkip to conversation

perf/s390: Regression: Move uid filtering to BPF filters

PATCH Superseded Ilya Leoshkevich 5 participants 9 messages Aug 5, 2025 – Aug 6, 2025

Subsystems (4)

v3 of 5 Superseded Latest is v5 →

lore
Share & tools
lore
#0 lore raw

v3 cover perf/s390: Regression: Move uid filtering to BPF filters

v2: https://lore.kernel.org/bpf/[email protected]/
v2 -> v3: Use no_ioctl_enable in perf.

v1: https://lore.kernel.org/bpf/[email protected]/
v1 -> v2: Introduce no_ioctl_enable (Jiri).

Hi,

This series fixes a regression caused by moving UID filtering to BPF. The regression affects all events that support auxiliary data, most notably, "cycles" events on s390, but also PT events on Intel. The symptom is missing events when UID filtering is enabled.

Patch 1 introduces a new option for the bpf_program__attach_perf_event_opts() function.
Ppatch 2 makes use of it in perf, and also contains a lot of technical details of why exactly the prolblem is occurring.

Thanks to Thomas Richter for the investigation and the initial version of this fix, and to Jiri Olsa for suggestions.

Best regards,
Ilya

Ilya Leoshkevich (2):
libbpf: Add the ability to suppress perf event enablement perf bpf-filter: Enable events manually

 tools/lib/bpf/libbpf.c       | 13 ++++++++-----
 tools/lib/bpf/libbpf.h       |  4 +++-
 tools/perf/util/bpf-filter.c |  5 ++++-
 3 files changed, 15 insertions(+), 7 deletions(-)
Signature · 1 line
2.50.1
#1 lore raw

PATCH v3 1/2 libbpf: Add the ability to suppress perf event enablement

Automatically enabling a perf event after attaching a BPF prog to it is not always desirable.

Add a new no_ioctl_enable field to struct bpf_perf_event_opts. While introducing ioctl_enable instead would be nicer in that it would avoid a double negation in the implementation, it would make DECLARE_LIBBPF_OPTS() less efficient.

---
 tools/lib/bpf/libbpf.c | 13 ++++++++-----
 tools/lib/bpf/libbpf.h |  4 +++-
 2 files changed, 11 insertions(+), 6 deletions(-)
tools/lib/bpf/libbpf.c +8 -5
index fb4d92c5c339..414c566c4650 100644
@@ -10965,11 +10965,14 @@ struct bpf_link *bpf_program__attach_perf_event_opts(const struct bpf_program *p
 		}
 		link->link.fd = pfd;
 	}
-	if (ioctl(pfd, PERF_EVENT_IOC_ENABLE, 0) < 0) {
-		err = -errno;
-		pr_warn("prog '%s': failed to enable perf_event FD %d: %s\n",
-			prog->name, pfd, errstr(err));
-		goto err_out;
+
+	if (!OPTS_GET(opts, no_ioctl_enable, false)) {
+		if (ioctl(pfd, PERF_EVENT_IOC_ENABLE, 0) < 0) {
+			err = -errno;
+			pr_warn("prog '%s': failed to enable perf_event FD %d: %s\n",
+				prog->name, pfd, errstr(err));
+			goto err_out;
+		}
 	}
 
 	return &link->link;
tools/lib/bpf/libbpf.h +3 -1
index d1cf813a057b..2d3cc436cdbf 100644
@@ -499,9 +499,11 @@ struct bpf_perf_event_opts {
 	__u64 bpf_cookie;
 	/* don't use BPF link when attach BPF program */
 	bool force_ioctl_attach;
+	/* don't automatically enable the event */
+	bool no_ioctl_enable;
 	size_t :0;
 };
-#define bpf_perf_event_opts__last_field force_ioctl_attach
+#define bpf_perf_event_opts__last_field no_ioctl_enable
 
 LIBBPF_API struct bpf_link *
 bpf_program__attach_perf_event(const struct bpf_program *prog, int pfd);
Signature · 1 line
2.50.1
#2 lore raw

Re: [PATCH v3 1/2] libbpf: Add the ability to suppress perf event enablement

Quoted 47 lines · Ilya Leoshkevich

Automatically enabling a perf event after attaching a BPF prog to it is not always desirable.

Add a new no_ioctl_enable field to struct bpf_perf_event_opts. While introducing ioctl_enable instead would be nicer in that it would avoid a double negation in the implementation, it would make DECLARE_LIBBPF_OPTS() less efficient.

---
 tools/lib/bpf/libbpf.c | 13 ++++++++-----
 tools/lib/bpf/libbpf.h |  4 +++-
 2 files changed, 11 insertions(+), 6 deletions(-)
tools/lib/bpf/libbpf.c +8 -5
index fb4d92c5c339..414c566c4650 100644
@@ -10965,11 +10965,14 @@ struct bpf_link *bpf_program__attach_perf_event_opts(const struct bpf_program *p
                }
                link->link.fd = pfd;
        }
-       if (ioctl(pfd, PERF_EVENT_IOC_ENABLE, 0) < 0) {
-               err = -errno;
-               pr_warn("prog '%s': failed to enable perf_event FD %d: %s\n",
-                       prog->name, pfd, errstr(err));
-               goto err_out;
+
+       if (!OPTS_GET(opts, no_ioctl_enable, false)) {
+               if (ioctl(pfd, PERF_EVENT_IOC_ENABLE, 0) < 0) {
+                       err = -errno;
+                       pr_warn("prog '%s': failed to enable perf_event FD %d: %s\n",
+                               prog->name, pfd, errstr(err));
+                       goto err_out;
+               }
        }
 
        return &link->link;
tools/lib/bpf/libbpf.h +0 -0
index d1cf813a057b..2d3cc436cdbf 100644

tools/lib/bpf/libbpf.h struct bpf_perf_event_opts { · line 503

Quoted 5 lines
tools/lib/bpf/libbpf.h +2 -0
@@ -499,9 +499,11 @@ struct bpf_perf_event_opts {
        __u64 bpf_cookie;
        /* don't use BPF link when attach BPF program */
        bool force_ioctl_attach;
+       /* don't automatically enable the event */
+       bool no_ioctl_enable;

The patch logic looks fine, but I feel the knob name is too implementation oriented.
imo "dont_auto_enable" is more descriptive and easier to reason about.

Let's wait for Eduard/Andrii reviews. This patch has to go via bpf trees first while the latter via perf.

maintainer Acked-by
#3 lore raw

Re: [PATCH v3 1/2] libbpf: Add the ability to suppress perf event enablement

Quoted 10 lines · Alexei Starovoitov
Quoted 9 lines · Ilya Leoshkevich

Automatically enabling a perf event after attaching a BPF prog to it is not always desirable.

Add a new no_ioctl_enable field to struct bpf_perf_event_opts. While introducing ioctl_enable instead would be nicer in that it would avoid a double negation in the implementation, it would make DECLARE_LIBBPF_OPTS() less efficient.

Quoted 5 lines
Quoted 5 lines

---

[...]

Quoted 14 lines

tools/lib/bpf/libbpf.h struct bpf_perf_event_opts { · line 503

Quoted 8 lines
tools/lib/bpf/libbpf.h +2 -0
@@ -499,9 +499,11 @@ struct bpf_perf_event_opts {
        __u64 bpf_cookie;
        /* don't use BPF link when attach BPF program */
        bool force_ioctl_attach;
+       /* don't automatically enable the event */
+       bool no_ioctl_enable;

The patch logic looks fine, but I feel the knob name is too implementation oriented.
imo "dont_auto_enable" is more descriptive and easier to reason about.

Quoted 2 lines

Let's wait for Eduard/Andrii reviews. This patch has to go via bpf trees first while the latter via perf.

Agree with Alexei,
something like "dont_enable" should be simpler to read.

#4 lore raw

PATCH v3 2/2 perf bpf-filter: Enable events manually

In reply to Ilya Leoshkevich

On linux-next
commit b4c658d4d63d61 ("perf target: Remove uid from target") introduces a regression on s390. In fact the regression exists on all platforms when the event supports auxiliary data gathering.

Command

   # ./perf record -u 0 -aB --synth=no -- ./perf test -w thloop
   [ perf record: Woken up 1 times to write data ]
   [ perf record: Captured and wrote 0.011 MB perf.data ]
   # ./perf report --stats | grep SAMPLE
   #

does not generate samples in the perf.data file.
On x86 command

  # sudo perf record -e intel_pt// -u 0 ls

is broken too.

Looking at the sequence of calls in 'perf record' reveals this behavior:

1. The event 'cycles' is created and enabled:

record__open()

   +-> evlist__apply_filters()
       +-> perf_bpf_filter__prepare()
	   +-> bpf_program.attach_perf_event()
	       +-> bpf_program.attach_perf_event_opts()
	           +-> __GI___ioctl(..., PERF_EVENT_IOC_ENABLE, ...)

The event 'cycles' is enabled and active now. However the event's ring-buffer to store the samples generated by hardware is not allocated yet.

2. The event's fd is mmap()ed to create the ring buffer:

record__open()

   +-> record__mmap()
       +-> record__mmap_evlist()
	   +-> evlist__mmap_ex()
	       +-> perf_evlist__mmap_ops()
	           +-> mmap_per_cpu()
	               +-> mmap_per_evsel()
	                   +-> mmap__mmap()
	                       +-> perf_mmap__mmap()
	                           +-> mmap()

This allocates the ring buffer for the event 'cycles'. With mmap() the kernel creates the ring buffer:

perf_mmap(): kernel function to create the event's ring
| buffer to save the sampled data.
|

   +-> ring_buffer_attach(): Allocates memory for ring buffer.
       |        The PMU has auxiliary data setup function. The
       |        has_aux(event) condition is true and the PMU's
       |        stop() is called to stop sampling. It is not
       |        restarted:
       |
       |        if (has_aux(event))
       |                perf_event_stop(event, 0);
       |
       +-> cpumsf_pmu_stop():

Hardware sampling is stopped. No samples are generated and saved anymore.

3. After the event 'cycles' has been mapped, the event is enabled a second time in:

__cmd_record()

   +-> evlist__enable()
       +-> __evlist__enable()
	   +-> evsel__enable_cpu()
	       +-> perf_evsel__enable_cpu()
	           +-> perf_evsel__run_ioctl()
	               +-> perf_evsel__ioctl()
	                   +-> __GI___ioctl(., PERF_EVENT_IOC_ENABLE, .)

The second

      ioctl(fd, PERF_EVENT_IOC_ENABLE, 0);

is just a NOP in this case. The first invocation in (1.) sets the event::state to PERF_EVENT_STATE_ACTIVE. The kernel functions

perf_ioctl()

   +-> _perf_ioctl()
       +-> _perf_event_enable()
           +-> __perf_event_enable()

return immediately because event::state is already set to PERF_EVENT_STATE_ACTIVE.

This happens on s390, because the event 'cycles' offers the possibility to save auxilary data. The PMU callbacks setup_aux() and free_aux() are defined. Without both callback functions, cpumsf_pmu_stop() is not invoked and sampling continues.

To remedy this, remove the first invocation of

ioctl(..., PERF_EVENT_IOC_ENABLE, ...).

in step (1.) Create the event in step (1.) and enable it in step (3.) after the ring buffer has been mapped.

Output after:

 # ./perf record -aB --synth=no -u 0 -- ./perf test -w thloop 2
 [ perf record: Woken up 3 times to write data ]
 [ perf record: Captured and wrote 0.876 MB perf.data ]
 # ./perf  report --stats | grep SAMPLE
              SAMPLE events:      16200  (99.5%)
              SAMPLE events:      16200
 #

The software event succeeded both before and after the patch:

 # ./perf record -e cpu-clock -aB --synth=no -u 0 -- \
					  ./perf test -w thloop 2
 [ perf record: Woken up 7 times to write data ]
 [ perf record: Captured and wrote 2.870 MB perf.data ]
 # ./perf  report --stats | grep SAMPLE
              SAMPLE events:      53506  (99.8%)
              SAMPLE events:      53506
 #
Fixes 63f2f5ee856ba ("libbpf: add ability to attach/detach BPF program to perf event")
---
 tools/perf/util/bpf-filter.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
tools/perf/util/bpf-filter.c +4 -1
index d0e013eeb0f7..d480ccaf3662 100644
@@ -451,6 +451,8 @@ int perf_bpf_filter__prepare(struct evsel *evsel, struct target *target)
 	struct bpf_link *link;
 	struct perf_bpf_filter_entry *entry;
 	bool needs_idx_hash = !target__has_cpu(target);
+	DECLARE_LIBBPF_OPTS(bpf_perf_event_opts, pe_opts,
+			    .no_ioctl_enable = true);
 
 	entry = calloc(MAX_FILTERS, sizeof(*entry));
 	if (entry == NULL)
@@ -522,7 +524,8 @@ int perf_bpf_filter__prepare(struct evsel *evsel, struct target *target)
 	prog = skel->progs.perf_sample_filter;
 	for (x = 0; x < xyarray__max_x(evsel->core.fd); x++) {
 		for (y = 0; y < xyarray__max_y(evsel->core.fd); y++) {
-			link = bpf_program__attach_perf_event(prog, FD(evsel, x, y));
+			link = bpf_program__attach_perf_event_opts(prog, FD(evsel, x, y),
+								   &pe_opts);
 			if (IS_ERR(link)) {
 				pr_err("Failed to attach perf sample-filter program\n");
 				ret = PTR_ERR(link);
Signature · 1 line
2.50.1
#5 lore raw

Re: [PATCH v3 2/2] perf bpf-filter: Enable events manually

On Tue, Aug 05, 2025 at 02:54:05PM +0200, Ilya Leoshkevich wrote:

Hi Thomas,

The below comments date to the initial version, so the question is rather to you:

Quoted 1 line

On linux-next

This line is extra.

Quoted 3 lines

commit b4c658d4d63d61 ("perf target: Remove uid from target") introduces a regression on s390. In fact the regression exists on all platforms when the event supports auxiliary data gathering.

So which commit it actually fixes: the above, the below or the both?

Quoted 1 line
Fixes 63f2f5ee856ba ("libbpf: add ability to attach/detach BPF program to perf event")

Thanks!

#6 lore raw

Re: [PATCH v3 2/2] perf bpf-filter: Enable events manually

Quoted 10 lines · Alexander Gordeev

On Tue, Aug 05, 2025 at 02:54:05PM +0200, Ilya Leoshkevich wrote:

Hi Thomas,

The below comments date to the initial version, so the question is rather to you:

Quoted 1 line

On linux-next

This line is extra.

I just wanted to let readers know which repo to look at.

Quoted 11 lines
Quoted 4 lines

commit b4c658d4d63d61 ("perf target: Remove uid from target") introduces a regression on s390. In fact the regression exists on all platforms when the event supports auxiliary data gathering.

So which commit it actually fixes: the above, the below or the both?

Quoted 1 line
Fixes 63f2f5ee856ba ("libbpf: add ability to attach/detach BPF program to perf event")

Thanks!

Good question! Pick what you like... :-)

The issue in question originates from a patch set of 10 patches. The patch set rebuilds event sample with filtering and migrates from perf tool's selective process picking to more generic eBPF filtering using eBPF programs hooked to perf events.

To be precise, the issue Ilya's patch fixes is this:

Fixes 63f2f5ee856ba ("libbpf: add ability to attach/detach BPF program to perf event")

However the issue (perf failure) does *NOT* show up until this patch is applied:
commit b4c658d4d63d61 ("perf target: Remove uid from target")

There are some patches in between the two (when you look at the complete patch set), but they do not affect the result.

Hope that helps.

Signature · 9 lines
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH

Vorsitzender des Aufsichtsrats: Wolfgang Wendt

Geschäftsführung: David Faller

Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
#7 lore raw

Re: [PATCH v3 2/2] perf bpf-filter: Enable events manually

Quoted 36 lines · Thomas Richter
Quoted 10 lines · Alexander Gordeev

On Tue, Aug 05, 2025 at 02:54:05PM +0200, Ilya Leoshkevich wrote:

Hi Thomas,

The below comments date to the initial version, so the question is rather to you:

Quoted 1 line

On linux-next

This line is extra.

I just wanted to let readers know which repo to look at.

Quoted 6 lines
Quoted 5 lines

commit b4c658d4d63d61 ("perf target: Remove uid from target") introduces a regression on s390. In fact the regression exists on all platforms when the event supports auxiliary data gathering.

Quoted 8 lines

So which commit it actually fixes: the above, the below or the both?

Quoted 2 lines
Fixes 63f2f5ee856ba ("libbpf: add ability to attach/detach BPF

program to perf event")

Thanks!

Good question!  Pick what you like... :-)

The issue in question originates from a patch set of 10 patches. The patch set rebuilds event sample with filtering and migrates from perf tool's selective process picking to more generic eBPF filtering using eBPF programs hooked to perf events.

Quoted 7 lines

To be precise, the issue Ilya's  patch fixes is this:

Fixes 63f2f5ee856ba ("libbpf: add ability to attach/detach BPF

program to perf event")

However the issue (perf failure) does *NOT* show up until this patch is applied:
commit b4c658d4d63d61 ("perf target: Remove uid from target")

I think I will switch the Fixes: tag to b4c658d4d63d61 then, because IIUC it is one of the factors that drives backporting decisions, and it does not make too much sense to backport it to earlier kernels.

Quoted 5 lines

There are some patches in between the two (when you look at the complete patch set),
but they do not affect the result.

Hope that helps.

Tested-by on the v3 series
#8 lore raw
In reply to Ilya Leoshkevich
Quoted 8 lines · Ilya Leoshkevich

v2: https://lore.kernel.org/bpf/[email protected]/
v2 -> v3: Use no_ioctl_enable in perf.

v1: https://lore.kernel.org/bpf/[email protected]/
v1 -> v2: Introduce no_ioctl_enable (Jiri).

Hi,

Quoted 8 lines

This series fixes a regression caused by moving UID filtering to BPF. The regression affects all events that support auxiliary data, most notably, "cycles" events on s390, but also PT events on Intel. The symptom is missing events when UID filtering is enabled.

Patch 1 introduces a new option for the bpf_program__attach_perf_event_opts() function.
Ppatch 2 makes use of it in perf, and also contains a lot of technical

Typo Patch

Quoted 1 line

details of why exactly the prolblem is occurring.

Typo problem

Quoted 7 lines

Thanks to Thomas Richter for the investigation and the initial version of this fix, and to Jiri Olsa for suggestions.

Best regards,
Ilya

Quoted 9 lines

Ilya Leoshkevich (2):
libbpf: Add the ability to suppress perf event enablement perf bpf-filter: Enable events manually

 tools/lib/bpf/libbpf.c       | 13 ++++++++-----
 tools/lib/bpf/libbpf.h       |  4 +++-
 tools/perf/util/bpf-filter.c |  5 ++++-
 3 files changed, 15 insertions(+), 7 deletions(-)

Thanks for taking over!!!
For the whole series

Signature · 9 lines
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH

Vorsitzender des Aufsichtsrats: Wolfgang Wendt

Geschäftsführung: David Faller

Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294