All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: "Hill, Steven " <steven.hill@collins.com>
Cc: "linux-hardening@vger.kernel.org"
	<linux-hardening@vger.kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [RFC] gcc-plugins patch for compiler versioning.
Date: Thu, 25 Sep 2025 17:03:27 -0700	[thread overview]
Message-ID: <202509251701.0CC2424@keescook> (raw)
In-Reply-To: <BN0P110MB2020D78705BB39062BF8D107FD1FA@BN0P110MB2020.NAMP110.PROD.OUTLOOK.COM>

On Thu, Sep 25, 2025 at 05:00:35PM +0000, Hill, Steven  wrote:
> Hello.
> 
> Would like to have comments on the attached patch. There could be another
> option for checking both gcc and glibc versions. Just wanted comments before
> doing anything further. I am not on the mailing list, so please CC: on any
> replies. Thank you.
> 
> -Steve
> 
> 
> From b1ac0805d70aaa2e1500a071f63c88bcaa76754e Mon Sep 17 00:00:00 2001
> From: "Steven J. Hill" <steven.hill@collins.com>
> Date: Tue, 23 Sep 2025 18:21:09 -0500
> Subject: [PATCH] gcc-plugins: Relax constraints on plugin compatibility.
> 
> The compatibility check for gcc plugins is too inflexible,
> and a lot of times wrong. Add ability to let the user choose
> how stringent compatibility is.

Why is it wrong a lot? I'm not sure I understand what problem is being
solved here?

-Kees

-- 
Kees Cook

      reply	other threads:[~2025-09-26  0:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 17:00 [RFC] gcc-plugins patch for compiler versioning Hill, Steven 
2025-09-26  0:03 ` 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=202509251701.0CC2424@keescook \
    --to=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=steven.hill@collins.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.