public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: Thorsten Blum <thorsten.blum@linux.dev>,
	Bill Wendling <morbo@google.com>, Peter Rosin <peda@axentia.se>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-hardening@vger.kernel.org"
	<linux-hardening@vger.kernel.org>
Subject: Re: [RESEND PATCH] mux: Convert mux_control_ops to a flex array member in mux_chip
Date: Wed, 5 Mar 2025 14:42:42 -0800	[thread overview]
Message-ID: <202503051438.01AD65C@keescook> (raw)
In-Reply-To: <20C5E493-4FB3-4347-844B-1AFE6B9FCDA4@oracle.com>

On Wed, Mar 05, 2025 at 05:31:57PM +0000, Qing Zhao wrote:
> This does look like a bug in the compiler, could you please file a bug against GCC on this?

Okay, thanks for taking a looking!

GCC: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119132
Clang: https://github.com/llvm/llvm-project/issues/129951

-Kees

-- 
Kees Cook

  reply	other threads:[~2025-03-05 22:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-02 23:02 [RESEND PATCH] mux: Convert mux_control_ops to a flex array member in mux_chip Thorsten Blum
2025-03-03 18:44 ` Kees Cook
2025-03-04  8:58   ` Thorsten Blum
2025-03-05  4:57     ` Kees Cook
2025-03-05 17:31       ` Qing Zhao
2025-03-05 17:31       ` Qing Zhao
2025-03-05 22:42         ` Kees Cook [this message]
2025-03-07 11:32   ` Thorsten Blum
2025-04-07 18:20     ` Kees Cook
2025-04-13 12:42       ` Thorsten Blum
2025-04-29 11:55         ` Thorsten Blum
  -- strict thread matches above, loose matches on Subject: below --
2025-03-18 16:27 Thorsten Blum

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=202503051438.01AD65C@keescook \
    --to=kees@kernel.org \
    --cc=gustavoars@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morbo@google.com \
    --cc=peda@axentia.se \
    --cc=qing.zhao@oracle.com \
    --cc=thorsten.blum@linux.dev \
    /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