From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: filemap.c:(.text+0x4960): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
Date: Sat, 16 Dec 2023 03:13:03 +0000 [thread overview]
Message-ID: <ZX0Vv3IyOi+Bp10Q@casper.infradead.org> (raw)
In-Reply-To: <202312161000.zSaZMSRO-lkp@intel.com>
On Sat, Dec 16, 2023 at 10:11:04AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 3bd7d748816927202268cb335921f7f68b3ca723
> commit: 2580d554585c52a644839864ef9238af5b030ebc mm: use folio_xor_flags_has_waiters() in folio_end_writeback()
> date: 8 weeks ago
> config: csky-buildonly-randconfig-r002-20220807 (https://download.01.org/0day-ci/archive/20231216/202312161000.zSaZMSRO-lkp@intel.com/config)
> compiler: csky-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231216/202312161000.zSaZMSRO-lkp@intel.com/reproduce)
This seems like a general problem with (some configurations of?) csky.
I don't think I've made anything worse. I don't intend to investigate
this further.
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202312161000.zSaZMSRO-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> mm/filemap.o: in function `folio_end_writeback':
> >> filemap.c:(.text+0x4960): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x4978): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x4990): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x49a2): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x49b8): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x49d2): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x49f2): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x4a0c): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x4a4a): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x4a50): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
> filemap.c:(.text+0x4a66): additional relocation overflows omitted from the output
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-16 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 2:11 filemap.c:(.text+0x4960): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table' kernel test robot
2023-12-16 3:13 ` Matthew Wilcox [this message]
2023-12-16 5:58 ` Philip Li
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=ZX0Vv3IyOi+Bp10Q@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).