From: SeongJae Park <sj@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [sj:damon/next 27/28] hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x42da0): cannot reach 0000a892_bpf_trace_run2+0, recompile with -ffunction-sections
Date: Mon, 9 Oct 2023 23:56:49 +0000 [thread overview]
Message-ID: <20231009235650.9301-1-sj@kernel.org> (raw)
In-Reply-To: <202310090405.GXbIXpan-lkp@intel.com>
Hi Robot,
On Mon, 9 Oct 2023 04:40:31 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/next
> head: b51b81a2d623ddeda365270f24748bea23a93a2f
> commit: 8a198cce537de4f58f1cd791cd05347320a025b3 [27/28] mm/damon/sysfs: avoid empty scheme tried regions for large apply interval
> config: parisc-allyesconfig (https://download.01.org/0day-ci/archive/20231009/202310090405.GXbIXpan-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231009/202310090405.GXbIXpan-lkp@intel.com/reproduce)
>
> 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/202310090405.GXbIXpan-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x42da0): cannot reach 0000a892_bpf_trace_run2+0, recompile with -ffunction-sections
> hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x42da0): cannot handle R_PARISC_PCREL17F for bpf_trace_run2
> hppa-linux-ld: final link failed: bad value
Thank you for this report! Nevertheless, I was unable to reproduce the issue.
It indeed fails the build, but with a different error. Also, I get the same
error on the baseline of the tree, namely mm-unstable (specifically, commit
e0b0922d61a8).
hppa-linux-ld: drivers/mtd/nand/raw/nand_base.o: in function `nand_do_write_ops':
(.text+0x4a24): undefined reference to `.L874'
make[3]: *** [/home/sjpark/linux/scripts/Makefile.vmlinux:36: vmlinux] Error 1
make[3]: Target '__default' not remade because of errors.
make[2]: *** [/home/sjpark/linux/Makefile:1165: vmlinux] Error 2
make[2]: Target '__all' not remade because of errors.
make[1]: *** [/home/sjpark/linux/Makefile:234: __sub-make] Error 2
make[1]: Target '__all' not remade because of errors.
make[1]: Leaving directory '/home/sjpark/linux.parisc.out'
make: *** [Makefile:234: __sub-make] Error 2
make: Target '__all' not remade because of errors.
I'm also not sure how the commit you found could make such error, since the
commit doesn't touch any of xfs code.
$ git log 8a198cce537de4f58f1cd791cd05347320a025b3 --stat -1
commit 8a198cce537de4f58f1cd791cd05347320a025b3
Author: SeongJae Park <sj@kernel.org>
Date: Fri Oct 6 22:58:00 2023 +0000
mm/damon/sysfs: avoid empty scheme tried regions for large apply interval
Signed-off-by: SeongJae Park <sj@kernel.org>
mm/damon/sysfs-common.h | 2 ++
mm/damon/sysfs-schemes.c | 16 ++++++++++++++++
mm/damon/sysfs.c | 25 +++++++++++++++++++++----
3 files changed, 39 insertions(+), 4 deletions(-)
Anything I'm missing? Or, could this report be mistakenly made?
Thanks,
SJ
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2023-10-09 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202310090405.GXbIXpan-lkp@intel.com>
2023-10-09 23:56 ` SeongJae Park [this message]
2023-10-12 3:55 ` [sj:damon/next 27/28] hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x42da0): cannot reach 0000a892_bpf_trace_run2+0, recompile with -ffunction-sections Yujie Liu
2023-10-12 15:46 ` SeongJae Park
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=20231009235650.9301-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).