linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: kernel test robot <lkp@intel.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Marco Elver <elver@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [stable:linux-5.15.y 36/9999] arch/s390/kernel/vtime.c:132:2: error: expected absolute expression
Date: Tue, 23 May 2023 10:45:25 -0700	[thread overview]
Message-ID: <20230523174525.GA1388474@dev-arch.thelio-3990X> (raw)
In-Reply-To: <202305111519.04845F7@keescook>

On Thu, May 11, 2023 at 03:21:01PM -0700, Kees Cook wrote:
> On Thu, May 11, 2023 at 05:14:16PM +0800, kernel test robot wrote:
> > FYI, the error/warning still remains.
> > 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.15.y
> > head:   8a7f2a5c5aa1648edb4f2029c6ec33870afb7a95
> > commit: 33db9912ff7c491f839c89a08e98f755aa09598f [36/9999] ubsan: remove CONFIG_UBSAN_OBJECT_SIZE
> > [...]
> > >> arch/s390/kernel/vtime.c:132:2: error: cpu alternatives does not support instructions blocks > 254 bytes
> >            alternative_io("stpt %0\n .insn s,0xb2050000,%1\n",
> >            ^
> 
> Thanks for the report! I don't think the new errors are related to this
> removal, though. This patch was just disabling a potential build config.

Right, I am not really sure how the robot landed on this (perhaps there
was another error that was being exposed by CONFIG_UBSAN_OBJECT_SIZE
that disappeared with its removal?) but this is a problem with s390
specific code and clang's integrated assembler. I suspect it would be
fixed with one of the patches from this series that landed in 5.19 but I
have not looked too closely:

https://lore.kernel.org/20220511120532.2228616-1-hca@linux.ibm.com/
https://lore.kernel.org/Yot+xzLZETNTxNo+@osiris/

We use LLVM_IAS=0 for s390 on 5.15 in CI, hence why we do not see this.

Cheers,
Nathan


      reply	other threads:[~2023-05-23 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  9:14 kernel test robot
2023-05-11 22:21 ` Kees Cook
2023-05-23 17:45   ` Nathan Chancellor [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=20230523174525.GA1388474@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=elver@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.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