From mboxrd@z Thu Jan 1 00:00:00 1970 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 3FC9EC433F5 for ; Wed, 20 Apr 2022 01:00:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348145AbiDTBC6 (ORCPT ); Tue, 19 Apr 2022 21:02:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45280 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348190AbiDTBC5 (ORCPT ); Tue, 19 Apr 2022 21:02:57 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 427331EECE for ; Tue, 19 Apr 2022 18:00:13 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id CC69C61481 for ; Wed, 20 Apr 2022 01:00:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 233F6C385AA; Wed, 20 Apr 2022 01:00:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1650416412; bh=RjfgZtRBtVsGEVVvHCtrNYukohlE+AAUgjJ/b1cDpls=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=LcV04C4zEVO5XdlqywV/EC0KD2dXSZxYJ8nqUNfoKGhFgz4caKhG+0T3Rk5l0jg7b W6143zmxVopqPi80g57mnVuXsbBOx0D7LBrUaOQVCuUNX6g/r8ZdFLq4g4+czG59Sd Aci05rJ6pqVF5CB90qxIVylcaERHsPDO5j8WQUpPBYNrAmSvV/RIStyEGwXqOWNkZa lM+ugFK5HKK+9WI/Z4KDpT23c0XAACvkhs7Yc3aMuoi5daq2eJUECp5yC0FU0/yeu0 9Z67cL5BgH9tQOumMwXJGXtkhyGLfWdJB0PPIRc94tN3Ob+Ldq8zhc+Qoic2WnuxS2 jRq4jX6rdoLUA== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id E0D03E8DBDA; Wed, 20 Apr 2022 01:00:11 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH bpf-next v3 0/2] Ensure type tags are always ordered first in BTF From: patchwork-bot+netdevbpf@kernel.org Message-Id: <165041641191.4464.2434468387244993266.git-patchwork-notify@kernel.org> Date: Wed, 20 Apr 2022 01:00:11 +0000 References: <20220419164608.1990559-1-memxor@gmail.com> In-Reply-To: <20220419164608.1990559-1-memxor@gmail.com> To: Kumar Kartikeya Dwivedi Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net, yhs@fb.com Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Hello: This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov : On Tue, 19 Apr 2022 22:16:06 +0530 you wrote: > When iterating over modifiers, ensure that type tags can only occur at head of > the chain, and don't occur later, such that checking for them once in the start > tells us there are no more type tags in later modifiers. Clang already ensures > to emit such BTF, but user can craft their own BTF which violates such > assumptions if relied upon in the kernel. > > Changelog: > > [...] Here is the summary with links: - [bpf-next,v3,1/2] bpf: Ensure type tags precede modifiers in BTF https://git.kernel.org/bpf/bpf-next/c/eb596b090558 - [bpf-next,v3,2/2] selftests/bpf: Add tests for type tag order validation https://git.kernel.org/bpf/bpf-next/c/24fe983abe01 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html