From: Christoph Hellwig <hch@infradead.org>
To: Kees Cook <keescook@chromium.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Alexander Potapenko <glider@google.com>,
Alex Deucher <alexander.deucher@amd.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Arne Welzel <arne.welzel@corelight.com>,
Azeem Shaikh <azeemshaikh38@gmail.com>,
Bill Wendling <morbo@google.com>,
Conor Dooley <conor.dooley@microchip.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Fangrui Song <maskray@google.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Jakub Kicinski <kuba@kernel.org>, Jan Kara <jack@suse.cz>,
Joe Perches <joe@perches.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
John Stultz <jstultz@google.com>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Marco Elver <elver@google.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Simon Horman <simon.horman@corigine.com>,
Song Liu <song@kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
Tyrel Datwyler <tyreld@linux.ibm.com>,
Wyes Karny <wyes.karny@amd.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [GIT PULL] hardening updates for v6.5-rc1
Date: Thu, 29 Jun 2023 00:23:48 -0700 [thread overview]
Message-ID: <ZJ0xhCenJr+Dzs/8@infradead.org> (raw)
In-Reply-To: <202306280920.CB69D0F75@keescook>
On Wed, Jun 28, 2023 at 09:29:42AM -0700, Kees Cook wrote:
> > will be completely misued before we have a compiler actually supporting
> > available widely enough that we have it in the usual test bots.
>
> How do you see it being misused? Your mention of the test bots, I think,
> means you're worried the annotations will go unchecked for valid syntax?
Exactly.
> FWIW, I've got builders with the GCC and Clang patches that should catch
> this.
Are we going to get them wired up for automatic checks somewhere?
prev parent reply other threads:[~2023-06-29 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 0:34 Kees Cook
2023-06-28 6:20 ` Christoph Hellwig
2023-06-28 16:29 ` Kees Cook
2023-06-29 7:23 ` Christoph Hellwig [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=ZJ0xhCenJr+Dzs/8@infradead.org \
--to=hch@infradead.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexander.deucher@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=arne.welzel@corelight.com \
--cc=azeemshaikh38@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=dave.hansen@linux.intel.com \
--cc=djwong@kernel.org \
--cc=elver@google.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=glider@google.com \
--cc=gustavoars@kernel.org \
--cc=hdegoede@redhat.com \
--cc=jack@suse.cz \
--cc=joe@perches.com \
--cc=jstultz@google.com \
--cc=kadlec@netfilter.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=martin.petersen@oracle.com \
--cc=maskray@google.com \
--cc=mhiramat@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=palmer@rivosinc.com \
--cc=simon.horman@corigine.com \
--cc=song@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tyreld@linux.ibm.com \
--cc=wyes.karny@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®