From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Kees Cook <keescook@chromium.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
kernel test robot <lkp@intel.com>, Rich Felker <dalias@libc.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nicolas Schier <n.schier@avm.de>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] sh: Fix build with CONFIG_UBSAN=y
Date: Mon, 12 Feb 2024 19:45:22 +0100 [thread overview]
Message-ID: <178e0bebb1a85efebce1f504122ee190c068e0c9.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <202402121025.B0B6E47@keescook>
On Mon, 2024-02-12 at 10:26 -0800, Kees Cook wrote:
> > I just wanted to try reproduce the problem again with the reproducer in [1] as well
> > as with gcc-13.2.0, but your branch devel/overflow/ubsan-only no longer exists.
> >
> > Can you tell me where to find the patches now?
>
> Sure, they're in -next, but for an -rc2 based tree, see:
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=for-next/kspp
OK, thanks. I will give it a try with gcc-13.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2024-02-12 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 23:27 Kees Cook
2024-01-31 11:03 ` John Paul Adrian Glaubitz
2024-01-31 11:19 ` John Paul Adrian Glaubitz
2024-02-02 10:32 ` Kees Cook
2024-02-02 11:06 ` John Paul Adrian Glaubitz
2024-02-11 10:39 ` John Paul Adrian Glaubitz
2024-02-12 18:26 ` Kees Cook
2024-02-12 18:45 ` John Paul Adrian Glaubitz [this message]
2024-02-14 12:52 ` John Paul Adrian Glaubitz
2024-03-01 5:46 ` Liu, Yujie
2024-03-01 14:38 ` John Paul Adrian Glaubitz
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=178e0bebb1a85efebce1f504122ee190c068e0c9.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=n.schier@avm.de \
--cc=ysato@users.sourceforge.jp \
/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®