From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3748C2F25 for ; Sat, 14 May 2022 21:50:46 +0000 (UTC) Received: by mail-pg1-f182.google.com with SMTP id x8so7258154pgr.4 for ; Sat, 14 May 2022 14:50:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=/+6DXPA/etQO+MROO0HlzYfznWa6yuzqrt1lFu+IZCU=; b=X46GUAIQhLZgbIbW3ALwg7mUAi9aD9nKapR3TAoFkfjTlqeeHuVMk1gIo1XQ0yhsdL N0hnyu4RWWhHM3wtF0iEMRxtXOU5NkFees7jAbHlv51A9j241elTXlQkZcd3ZBf54JuI QmQxGgU2qsxD6sDjGZsdeqw6FNs+bdOxLbp9U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=/+6DXPA/etQO+MROO0HlzYfznWa6yuzqrt1lFu+IZCU=; b=v2rXo0WIKXDi2/fK69wghxZ8JxSNFjEtQhr7SMZJtKKuTmAEAVjCZp+jt4DqwLaJD/ KVwLWpRjEGDBIMeSlqTtDFRIHuwkdEoUOiFPsDUazaIEDLzJ8cBzTh0Mw6UdwYLAAU8u 8uCef8IgLJYkWGXwYiMurLT+CMUUlE3THIaeXJ78+gMY+7rvYYXY9iOfp79vJ44VbQb8 P9aY5Axtu2YW05UjlrBs4smov2TnA6hetUWsnv3PtaVfKE0Of2sVWm6Qgn19YCeqy6WJ RiYauGnfg/Pq+Hpn9H1Bref2TcoJ+ySrsx6bwlAkQ4hsBUHUtNhSnc+6ch+QJGOqBHK4 ypqw== X-Gm-Message-State: AOAM53152R+6FshkL0hOzOrEW/Fc2WCko3KLBG1+7AeerjWQNzZgt39P WErU+hrh1zWkt+1lzkFM0gEqIw== X-Google-Smtp-Source: ABdhPJyKT2rYy5VGyrBn24YvTCGmr7LDXKmlZ9vWWFE2j7T4CYJuXCvTnF4P3WJsCwUHfcUj11JmLg== X-Received: by 2002:a05:6a00:1709:b0:505:fa47:b611 with SMTP id h9-20020a056a00170900b00505fa47b611mr6064948pfc.65.1652565045739; Sat, 14 May 2022 14:50:45 -0700 (PDT) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id j13-20020a170902c3cd00b0015ea95948ebsm4116861plj.134.2022.05.14.14.50.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 14 May 2022 14:50:45 -0700 (PDT) Date: Sat, 14 May 2022 14:50:44 -0700 From: Kees Cook To: Sami Tolvanen Cc: linux-kernel@vger.kernel.org, Josh Poimboeuf , Peter Zijlstra , x86@kernel.org, Catalin Marinas , Will Deacon , Mark Rutland , Nathan Chancellor , Nick Desaulniers , Joao Moreira , Sedat Dilek , Steven Rostedt , linux-hardening@vger.kernel.org, linux-arm-kernel@lists.infradead.org, llvm@lists.linux.dev Subject: Re: [RFC PATCH v2 09/21] arm64: Add types to indirect called assembly functions Message-ID: <202205141450.C5287B6@keescook> References: <20220513202159.1550547-1-samitolvanen@google.com> <20220513202159.1550547-10-samitolvanen@google.com> Precedence: bulk X-Mailing-List: llvm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220513202159.1550547-10-samitolvanen@google.com> On Fri, May 13, 2022 at 01:21:47PM -0700, Sami Tolvanen wrote: > With CONFIG_CFI_CLANG, assembly functions indirectly called from C > code must be annotated with type identifiers to pass CFI checking. Use > SYM_TYPED_FUNC_START for indirectly called functions. > > Signed-off-by: Sami Tolvanen Sort of related to my question about SYM_TYPED_FUNC_START itself, how were these cases identified? Reviewed-by: Kees Cook -- Kees Cook