Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6D730C05027 for ; Thu, 9 Feb 2023 00:54:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230404AbjBIAyU (ORCPT ); Wed, 8 Feb 2023 19:54:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38894 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229813AbjBIAyS (ORCPT ); Wed, 8 Feb 2023 19:54:18 -0500 Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6BC49222FF for ; Wed, 8 Feb 2023 16:54:16 -0800 (PST) Received: by mail-yb1-xb2b.google.com with SMTP id q4so542368ybu.7 for ; Wed, 08 Feb 2023 16:54:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HA3fnt3w/WkldBLqUixquvviOvTsBAQjIdHUUjb56M0=; b=sBenSKQ7FVZf9KJQB47/1z3eFo5uPqCWNUETrOZxLzOJtcLUPNVIZaxX+GVCS8uFqv iwRXjPWW2bB7JalEf8dr+4OdWdJW799KnVv5wR3Re1phRxVIyLFcHw8DCeqrZtz8wpVy XIQufLeg9mKvB3udTuoMH/+0CfFZbJdy/ZyhssQ4fqr17mtOH/3uHYHZZM4TwzEBnk1c ETarg2Djh7AnXFAKIXF7pYXNcN+vvceHsCfOFtij66RhDNrLMs1FODaLt+CFqesZPH49 wQnMqvfxtvRKT7lRAJvvjBs1NxndyUcfpXc7Mg5lNSVf9hg2QrUDTpTa+8R2UV3OhcvX IYYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HA3fnt3w/WkldBLqUixquvviOvTsBAQjIdHUUjb56M0=; b=rn6ia1s9B8r6VePoStOOJfmR4s+AlLYjwofBVtzHtwLioVEA/iHrZG0K2oTZbDDi0g 2MsLpMByrfSZcZWQ3/pr/MiPlxkvzYSzdPdyq+kYmJu/Qo1bQc1TkNxb7VODQIwRDEQc ernHt9qgslZVTENL1QZ+AJqK5Kg4ka79vbzUnlZQf50lSpSZmDrEE9jNe0oq8WuUUP/3 Vt3EwXaVptk0TszuZedcLBrny6ITU1xnNWKhLSbYGhMx2vjhBanUd0JLiZb/BlJpzyLH c3R98ZcmBoEpYjwQs8KblTPGLuT1Ly/A8nCpAGgGSAysCbUvUQTkQZsjK36RGJIJnNBC 62jA== X-Gm-Message-State: AO0yUKWqKFxkJZPyoVJXPSWP9ROre6iLZ6rYCJUNrTtrebFixsm8fIoQ TDkwKbC6z2TT5AdNSfanvRlCed0/oHorQ7NosCha X-Google-Smtp-Source: AK7set9ZNH349+n5tqrkBZ3G/4EXSKW8hwOrbG7RXJtrVdxo+rv0LsXkOz6w3KeCd3ROkx+iQMrf5PG0n+BJqgs4m/M= X-Received: by 2002:a5b:b87:0:b0:8b6:6ae:3bbe with SMTP id l7-20020a5b0b87000000b008b606ae3bbemr1101327ybq.340.1675904055502; Wed, 08 Feb 2023 16:54:15 -0800 (PST) MIME-Version: 1.0 References: <20211120112738.45980-1-laoar.shao@gmail.com> <20211120112738.45980-8-laoar.shao@gmail.com> In-Reply-To: From: John Stultz Date: Wed, 8 Feb 2023 16:54:03 -0800 Message-ID: Subject: Re: [PATCH v2 7/7] tools/testing/selftests/bpf: replace open-coded 16 with TASK_COMM_LEN To: Alexei Starovoitov Cc: Yafang Shao , Andrew Morton , Network Development , bpf , "linux-perf-use." , Linux-Fsdevel , linux-mm , LKML , kernel test robot , kbuild test robot , Andrii Nakryiko , David Hildenbrand , Mathieu Desnoyers , Arnaldo Carvalho de Melo , Andrii Nakryiko , Michal Miroslaw , Peter Zijlstra , Steven Rostedt , Matthew Wilcox , Al Viro , Kees Cook , Petr Mladek , Kajetan Puchalski , Lukasz Luba , Qais Yousef , Daniele Di Proietto Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 8, 2023 at 4:11 PM Alexei Starovoitov wrote: > > On Wed, Feb 8, 2023 at 2:01 PM John Stultz wrote: > > > > On Sat, Nov 20, 2021 at 11:27:38AM +0000, Yafang Shao wrote: > > > As the sched:sched_switch tracepoint args are derived from the kernel, > > > we'd better make it same with the kernel. So the macro TASK_COMM_LEN is > > > converted to type enum, then all the BPF programs can get it through BTF. > > > > > > The BPF program which wants to use TASK_COMM_LEN should include the header > > > vmlinux.h. Regarding the test_stacktrace_map and test_tracepoint, as the > > > type defined in linux/bpf.h are also defined in vmlinux.h, so we don't > > > need to include linux/bpf.h again. > > > > > > Signed-off-by: Yafang Shao > > > Acked-by: Andrii Nakryiko > > > Acked-by: David Hildenbrand > > > Cc: Mathieu Desnoyers > > > Cc: Arnaldo Carvalho de Melo > > > Cc: Andrii Nakryiko > > > Cc: Michal Miroslaw > > > Cc: Peter Zijlstra > > > Cc: Steven Rostedt > > > Cc: Matthew Wilcox > > > Cc: David Hildenbrand > > > Cc: Al Viro > > > Cc: Kees Cook > > > Cc: Petr Mladek > > > --- > > > include/linux/sched.h | 9 +++++++-- > > > tools/testing/selftests/bpf/progs/test_stacktrace_map.c | 6 +++--- > > > tools/testing/selftests/bpf/progs/test_tracepoint.c | 6 +++--- > > > 3 files changed, 13 insertions(+), 8 deletions(-) > > > > Hey all, > > I know this is a little late, but I recently got a report that > > this change was causiing older versions of perfetto to stop > > working. > > > > Apparently newer versions of perfetto has worked around this > > via the following changes: > > https://android.googlesource.com/platform/external/perfetto/+/c717c93131b1b6e3705a11092a70ac47c78b731d%5E%21/ > > https://android.googlesource.com/platform/external/perfetto/+/160a504ad5c91a227e55f84d3e5d3fe22af7c2bb%5E%21/ > > > > But for older versions of perfetto, reverting upstream commit > > 3087c61ed2c4 ("tools/testing/selftests/bpf: replace open-coded 16 > > with TASK_COMM_LEN") is necessary to get it back to working. > > > > I haven't dug very far into the details, and obviously this doesn't > > break with the updated perfetto, but from a high level this does > > seem to be a breaking-userland regression. > > > > So I wanted to reach out to see if there was more context for this > > breakage? I don't want to raise a unnecessary stink if this was > > an unfortuante but forced situation. > > Let me understand what you're saying... > > The commit 3087c61ed2c4 did > > -/* Task command name length: */ > -#define TASK_COMM_LEN 16 > +/* > + * Define the task command name length as enum, then it can be visible to > + * BPF programs. > + */ > +enum { > + TASK_COMM_LEN = 16, > +}; > > > and that caused: > > cat /sys/kernel/debug/tracing/events/task/task_newtask/format > > to print > field:char comm[TASK_COMM_LEN]; offset:12; size:16; signed:0; > instead of > field:char comm[16]; offset:12; size:16; signed:0; > > so the ftrace parsing android tracing tool had to do: > > - if (Match(type_and_name.c_str(), R"(char [a-zA-Z_]+\[[0-9]+\])")) { > + if (Match(type_and_name.c_str(), > + R"(char [a-zA-Z_][a-zA-Z_0-9]*\[[a-zA-Z_0-9]+\])")) { > > to workaround this change. > Right? I believe so. > And what are you proposing? I'm not proposing anything. I was just wanting to understand more context around this, as it outwardly appears to be a user-breaking change, and that is usually not done, so I figured it was an issue worth raising. If the debug/tracing/*/format output is in the murky not-really-abi space, that's fine, but I wanted to know if this was understood as something that may require userland updates or if this was a unexpected side-effect. thanks -john