Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp461613iob; Wed, 11 May 2022 19:23:15 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxppucHPlQGL8GXCkXnA6HZjE/HYB9cl/d8rUh7ghcRYFEXCfA3/9wtJRyBwIcYptQFIMDI X-Received: by 2002:a05:6402:17d9:b0:428:bee6:ba48 with SMTP id s25-20020a05640217d900b00428bee6ba48mr9038104edy.205.1652322195109; Wed, 11 May 2022 19:23:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652322195; cv=none; d=google.com; s=arc-20160816; b=PwOTB1qH2xdLELaEUCwvZ7jNWQXNaA+BzpCPDMGvs+6VUnSjmkXQvj/SRhfqe1LZxO tC6oNxe/chvi5p0pM9YClMaXzZasnkm5DdsTIck/dz1Ti8s80tXN2dDK24IibF6dtuq7 AsZ9jIa/feBew0kskT/Rnvm7cU7ScreG5fSWfGIae11cv2IHFA2kAA28v9CFu0z7oTUz 51MZ1hkYg2LidxIuZDjhavNP7p7mXiZv5sCacFOUaKRAtYNdsNiQh64sxGkr5WZm4ZNs nbNmJfNAYT0RAT9XokbAFdNvYciiduJu1Q2Yj28tWX2Mg2cddQCIGagRbnatekhI4JcP 8n/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=kH9OohPfXgK2fOqvMs876VLdS4ytX/lNxe9AdFrucOE=; b=S4tbKLtedBhkO7aAP7EkmFH24bcM+KqFdz+YfuG4IAxCjLDSx79I58L59lDz2aOLB4 bgRyPTuAGs8k5DaGO47KHuaweHiXNBFHMf+46ImOXy1UZZWqTWJs/qKn/ihH3a+Vd4l9 hBFDfzaOVQTXMKmXrFZc02bJhSGV3FNXdzsN0nqA2XSmSQvAOlNNIz+1F04xX8KqMCOH /gtMcWVTj6TRvD5lmxXEo7Jdd7SJxQKdPDBrhHsPEifDeXcRANKQbEXTzRp6rNpUn1du v9/YenFKEQP5h+mkE8RoMZKE2AUX9JUPpGuk6X3bQTwlKe3mQ8B+/elyR8PgwFCQdmkV J4NQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=veojJr+R; dkim=neutral (no key) header.i=@linutronix.de header.b=gpFs+rwc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x22-20020a05640226d600b00427c0e31f93si5025882edd.452.2022.05.11.19.22.48; Wed, 11 May 2022 19:23:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=veojJr+R; dkim=neutral (no key) header.i=@linutronix.de header.b=gpFs+rwc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349419AbiEKXlJ (ORCPT + 99 others); Wed, 11 May 2022 19:41:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41234 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349451AbiEKXlB (ORCPT ); Wed, 11 May 2022 19:41:01 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 699792CC98 for ; Wed, 11 May 2022 16:40:59 -0700 (PDT) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1652312457; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=kH9OohPfXgK2fOqvMs876VLdS4ytX/lNxe9AdFrucOE=; b=veojJr+RXkl7uopde/STRTEdqzrV3J3lqr+LLlfBb0FLHamC6kQ2Ywghn6j1N0twONog8h +tHD1pQLnUSFRJxK2kEGRe63rVVnioRqX9DrVXtSQ+sQDgEwfos0LvWiG0/xCp4gZUmX+/ UT2Yh0GdlZqBJTPcXsyxxAgM9vbZuHcPTVm+tueiHYzpWxGzXxUCwDTcyVbOhMFHITXS6k iahSA8yHj4reSmqmRdqlsvkGPvyJtLA9KwoI0zg6pveC9lMKCaeUeS/yTiQWW7y0KOE8CN t7R0vimhhtoby8PGCU/9ZNqK4TxQmK2DLZ2FJtf8N4FLv1h0wfY255bNgwpk2Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1652312457; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=kH9OohPfXgK2fOqvMs876VLdS4ytX/lNxe9AdFrucOE=; b=gpFs+rwcRqxzTdGGf+UKbSVg2pfrmnuNGIdFmZc0pnr+RN1vxwkpwSJD6koI080l9zIDY7 MyjGv8K9tkszMLAg== To: Delyan Kratunov , "peterz@infradead.org" Cc: "dietmar.eggemann@arm.com" , "bigeasy@linutronix.de" , "keescook@chromium.org" , "qais.yousef@arm.com" , Delyan Kratunov , "andrii@kernel.org" , "x86@kernel.org" , "vincent.guittot@linaro.org" , "akpm@linux-foundation.org" , "adharmap@quicinc.com" , "alexei.starovoitov@gmail.com" , "andrii.nakryiko@gmail.com" , "ast@kernel.org" , "Kenta.Tada@sony.com" , "rdunlap@infradead.org" , "linux-kernel@vger.kernel.org" , "bristot@redhat.com" , "ebiederm@xmission.com" , "mingo@kernel.org" , "rostedt@goodmis.org" , "ed.tsai@mediatek.com" , "legion@kernel.org" , "acme@kernel.org" , "u.kleine-koenig@pengutronix.de" , "valentin.schneider@arm.com" , "juri.lelli@redhat.com" , "namhyung@kernel.org" Subject: Re: [PATCH v2] sched/tracing: append prev_state to tp args instead In-Reply-To: References: <20220510082940.GA100765@worktop.programming.kicks-ass.net> Date: Thu, 12 May 2022 01:40:57 +0200 Message-ID: <8735hfy6wm.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 11 2022 at 18:28, Delyan Kratunov wrote: > Commit fa2c3254d7cf (sched/tracing: Don't re-read p->state when emitting > sched_switch event, 2022-01-20) added a new prev_state argument to the > sched_switch tracepoint, before the prev task_struct pointer. > > This reordering of arguments broke BPF programs that use the raw > tracepoint (e.g. tp_btf programs). The type of the second argument has > changed and existing programs that assume a task_struct* argument > (e.g. for bpf_task_storage access) will now fail to verify. > > If we instead append the new argument to the end, all existing programs > would continue to work and can conditionally extract the prev_state > argument on supported kernel versions. If we instead? ... would continue to work? https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#changelog https://www.kernel.org/doc/html/latest/process/submitting-patches.html#submittingpatches It's not too hard to actually follow documented rules. Something like this: "Undo the reordering and move the new argument last, which ensures that all existing programs continue to work." Hmm? What's worse is that the changelog is missing a clear statement that this is a one-time change which cannot be abused to turn tracepoints into unmodifiable ABI as you stated in: https://lore.kernel.org/lkml/CAEf4BzaEo+dxSRJZHQiXYrj-a3_B-eODZUxGh3HrnPjquMYFXQ@mail.gmail.com Thanks, tglx