From: Kees Cook <keescook@chromium.org>
To: Fangrui Song <maskray@google.com>
Cc: ndesaulniers@google.com, masahiroy@kernel.org,
linux-kbuild@vger.kernel.org, nathan@kernel.org,
linux-hardening@vger.kernel.org, jpoimboe@kernel.org,
llvm@lists.linux.dev, mbenes@suse.cz,
linux-kernel@vger.kernel.org, trix@redhat.com,
peterz@infradead.org
Subject: Re: [PATCH] ubsan: remove cc-option test for UBSAN_TRAP
Date: Wed, 17 May 2023 12:16:03 -0700 [thread overview]
Message-ID: <202305171215.7C58897@keescook> (raw)
In-Reply-To: <CAFP8O3JivZh+AAV7N90Nk7U2BHRNST6MRP0zHtfQ-Vj0m4+pDA@mail.gmail.com>
On Wed, May 17, 2023 at 12:09:35PM -0700, Fangrui Song wrote:
> On Wed, May 17, 2023 at 12:08 PM Fangrui Song <maskray@google.com> wrote:
> >
> > On Wed, May 17, 2023 at 12:02 PM Kees Cook <keescook@chromium.org> wrote:
> > >
> > > On Fri, 7 Apr 2023 14:54:06 -0700, Nick Desaulniers wrote:
> > > > -fsanitize-undefined-trap-on-error has been supported since GCC 5.1 and
> > > > Clang 3.2. The minimum supported version of these according to
> > > > Documentation/process/changes.rst is 5.1 and 11.0.0 respectively. Drop
> > > > this cc-option check.
> > > >
> > > >
> > >
> > > Applied to for-next/hardening, thanks!
> > >
> > > [1/1] ubsan: remove cc-option test for UBSAN_TRAP
> > > https://git.kernel.org/kees/c/08e4044243a6
> > >
> > > --
> > > Kees Cook
> > >
> > >
> >
> > For this -fsanitize-undefined-trap-on-error, I think we need a v2 patch that
> > tries -fsanitize-trap=all as well.
>
> Correction: -fsanitize-trap=undefined
>
> > -fsanitize-undefined-trap-on-error has been deprecated in Clang for 8
> > years, and at some point we will remove the option.
> >
> > GCC implements -fsanitize-trap=all later, but
> > -fsanitize-undefined-trap-on-error is documented as deprecated as
> > well.
Right now all the compilers support the old way, and I'd rather remove a
cc-option call than add two. :)
--
Kees Cook
next prev parent reply other threads:[~2023-05-17 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 21:54 [PATCH] ubsan: remove cc-option test for UBSAN_TRAP Nick Desaulniers
2023-04-07 21:58 ` Nathan Chancellor
2023-04-12 0:12 ` Fangrui Song
2023-04-12 15:12 ` Kees Cook
2023-04-12 18:13 ` Fangrui Song
2023-04-19 21:02 ` Fangrui Song
2023-05-17 19:02 ` Kees Cook
2023-05-17 19:08 ` Fangrui Song
2023-05-17 19:09 ` Fangrui Song
2023-05-17 19:16 ` Kees Cook [this message]
2023-05-17 19:22 ` Fangrui Song
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=202305171215.7C58897@keescook \
--to=keescook@chromium.org \
--cc=jpoimboe@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=mbenes@suse.cz \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=trix@redhat.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