From: kbuild test robot <lkp@intel.com>
To: "Julien, Grall," <julien.grall@arm.com>
Cc: kbuild-all@lists.01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Sasha Levin <alexander.levin@microsoft.com>
Subject: [linux-stable-rc:linux-5.4.y 1325/5512] lib/ubsan.c:422: undefined reference to `__ashrti3'
Date: Tue, 2 Jun 2020 04:01:36 +0800 [thread overview]
Message-ID: <202006020432.kv5XCaXD%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2481 bytes --]
Hi Julien,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
head: 1fd4226c4fe1a358bb8277e25ebb03950180443a
commit: 735e7a12a639c6c196ac1acf41f024f84281e491 [1325/5512] lib/ubsan: don't serialize UBSAN report
config: riscv-randconfig-c004-20200601 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
riscv64-linux-ld: lib/ubsan.o: in function `test_and_set_bit':
>> arch/riscv/include/asm/bitops.h:74: undefined reference to `__ashlti3'
riscv64-linux-ld: lib/ubsan.o: in function `get_signed_val':
>> lib/ubsan.c:422: undefined reference to `__ashrti3'
vim +422 lib/ubsan.c
c6d308534aef6c Andrey Ryabinin 2016-01-20 405
c6d308534aef6c Andrey Ryabinin 2016-01-20 406 void __ubsan_handle_load_invalid_value(struct invalid_value_data *data,
f0996bc2978e02 Andrey Ryabinin 2019-05-06 407 void *val)
c6d308534aef6c Andrey Ryabinin 2016-01-20 408 {
c6d308534aef6c Andrey Ryabinin 2016-01-20 409 char val_str[VALUE_LENGTH];
c6d308534aef6c Andrey Ryabinin 2016-01-20 410
c6d308534aef6c Andrey Ryabinin 2016-01-20 411 if (suppress_report(&data->location))
c6d308534aef6c Andrey Ryabinin 2016-01-20 412 return;
c6d308534aef6c Andrey Ryabinin 2016-01-20 413
735e7a12a639c6 Julien Grall 2019-12-04 414 ubsan_prologue(&data->location);
c6d308534aef6c Andrey Ryabinin 2016-01-20 415
c6d308534aef6c Andrey Ryabinin 2016-01-20 416 val_to_string(val_str, sizeof(val_str), data->type, val);
c6d308534aef6c Andrey Ryabinin 2016-01-20 417
c6d308534aef6c Andrey Ryabinin 2016-01-20 418 pr_err("load of value %s is not a valid value for type %s\n",
c6d308534aef6c Andrey Ryabinin 2016-01-20 419 val_str, data->type->type_name);
c6d308534aef6c Andrey Ryabinin 2016-01-20 420
735e7a12a639c6 Julien Grall 2019-12-04 421 ubsan_epilogue();
c6d308534aef6c Andrey Ryabinin 2016-01-20 @422 }
:::::: The code at line 422 was first introduced by commit
:::::: c6d308534aef6c99904bf5862066360ae067abc4 UBSAN: run-time undefined behavior sanity checker
:::::: TO: Andrey Ryabinin <aryabinin@virtuozzo.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33289 bytes --]
reply other threads:[~2020-06-01 20:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202006020432.kv5XCaXD%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=julien.grall@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/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