From: Kees Cook <keescook@chromium.org>
To: Kristina Martsenko <kristina.martsenko@arm.com>
Cc: "Daniel Díaz" <daniel.diaz@linaro.org>,
"Dan Li" <ashimida@linux.alibaba.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] lkdtm: Add CFI_BACKWARD to test ROP mitigations
Date: Wed, 14 Dec 2022 14:48:28 -0800 [thread overview]
Message-ID: <202212141448.03552F3@keescook> (raw)
In-Reply-To: <ba52dac5-2ce7-a567-41af-841b857abbed@arm.com>
On Fri, Dec 09, 2022 at 05:34:41PM +0000, Kristina Martsenko wrote:
> Subject: [PATCH] lkdtm: cfi: Make PAC test work with GCC 7 and 8
>
> The CFI test uses the branch-protection=none compiler attribute to
> disable PAC return address protection on a function. While newer GCC
> versions support this attribute, older versions (GCC 7 and 8) instead
> supported the sign-return-address=none attribute, leading to a build
> failure when the test is built with older compilers. Fix it by checking
> which attribute is supported and using the correct one.
>
> Fixes: 2e53b877dc12 ("lkdtm: Add CFI_BACKWARD to test ROP mitigations")
> Reported-by: Daniel Díaz <daniel.diaz@linaro.org>
> Signed-off-by: Kristina Martsenko <kristina.martsenko@arm.com>
> Link: https://lore.kernel.org/all/CAEUSe78kDPxQmQqCWW-_9LCgJDFhAeMoVBFnX9QLx18Z4uT4VQ@mail.gmail.com/
Thanks! Added to my tree.
> ---
> drivers/misc/lkdtm/cfi.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/misc/lkdtm/cfi.c b/drivers/misc/lkdtm/cfi.c
> index 5245cf6013c9..d4bb8e31a2fe 100644
> --- a/drivers/misc/lkdtm/cfi.c
> +++ b/drivers/misc/lkdtm/cfi.c
> @@ -54,7 +54,11 @@ static void lkdtm_CFI_FORWARD_PROTO(void)
> # ifdef CONFIG_ARM64_BTI_KERNEL
> # define __no_pac "branch-protection=bti"
> # else
> -# define __no_pac "branch-protection=none"
> +# ifdef CONFIG_CC_HAS_BRANCH_PROT_PAC_RET
> +# define __no_pac "branch-protection=none"
> +# else
> +# define __no_pac "sign-return-address=none"
> +# endif
> # endif
> # define __no_ret_protection __noscs __attribute__((__target__(__no_pac)))
> #else
>
--
Kees Cook
prev parent reply other threads:[~2022-12-14 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 0:11 [PATCH v2] lkdtm: Add CFI_BACKWARD to test ROP mitigations Kees Cook
2022-04-17 9:15 ` Dan Li
2022-04-18 21:51 ` Kees Cook
2022-12-07 0:28 ` Daniel Díaz
2022-12-08 6:22 ` Kees Cook
2022-12-09 17:34 ` Kristina Martsenko
2022-12-14 22:48 ` Kees Cook [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202212141448.03552F3@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=ashimida@linux.alibaba.com \
--cc=daniel.diaz@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kristina.martsenko@arm.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox