All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 14 Feb 2024 13:52:30 +0100	[thread overview]
Message-ID: <93572a771cb3a0b36a9213f18dd43c034c84cf6d.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <178e0bebb1a85efebce1f504122ee190c068e0c9.camel@physik.fu-berlin.de>

Hi Kees,

On Mon, 2024-02-12 at 19:45 +0100, John Paul Adrian Glaubitz wrote:
> 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.

I'm still unable to reproduce the error that the kernel test robot reported.

I'm using gcc-13:

glaubitz@node54:/data/home/glaubitz/linux-kees> sh4-linux-gcc
sh4-linux-gcc: fatal error: no input files
compilation terminated.
glaubitz@node54:/data/home/glaubitz/linux-kees> sh4-linux-gcc --version
sh4-linux-gcc (GCC) 13.2.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

glaubitz@node54:/data/home/glaubitz/linux-kees>

I checked out your tree and the for-next/kspp branch.

Then fetched the config that triggered the bug like this:

$ wget https://download.01.org/0day-ci/archive/20240131/202401310416.s8HLiLnC-lkp@intel.com/config -O .config

Building the kernel with "make -j32 uImage" works fine. No errors except for
some unreleated warnings that still need to be fixed.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2024-02-14 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 23:27 [PATCH] sh: Fix build with CONFIG_UBSAN=y 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
2024-02-14 12:52               ` John Paul Adrian Glaubitz [this message]
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=93572a771cb3a0b36a9213f18dd43c034c84cf6d.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 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.