From: "Theodore Ts'o" <tytso@mit.edu>
To: kernel test robot <lkp@intel.com>
Cc: Harshad Shirwadkar <harshadshirwadkar@gmail.com>,
kbuild-all@lists.01.org, linux-ext4@vger.kernel.org,
linux-um@lists.infradead.org, Andreas Dilger <adilger@dilger.ca>,
Ritesh Harjani <ritesh.list@gmail.com>
Subject: Re: [ext4:dev 13/28] mballoc.c:undefined reference to `atomic64_inc_386'
Date: Wed, 14 Apr 2021 16:20:37 -0400 [thread overview]
Message-ID: <YHdOlVdIfeqt7mJQ@mit.edu> (raw)
In-Reply-To: <202104122112.l9iI6DAy-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
On Mon, Apr 12, 2021 at 09:30:19PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
> head: fcdf3c34b7abdcbb49690c94c7fa6ce224dc9749
> commit: a6c75eaf11032f4a3d2b3ce2265a194ac6e4a7f0 [13/28] ext4: add mballoc stats proc file
> config: um-randconfig-r022-20210412 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=a6c75eaf11032f4a3d2b3ce2265a194ac6e4a7f0
> git remote add ext4 https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
> git fetch --no-tags ext4 dev
> git checkout a6c75eaf11032f4a3d2b3ce2265a194ac6e4a7f0
> # save the attached .config to linux build tree
> make W=1 ARCH=um
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> /usr/bin/ld: kernel/fork.o: in function `mm_init':
> fork.c:(.text+0x1294): undefined reference to `atomic64_set_386'
This appears to be a problem in the UM architecture. Tested using
linux.git (without any of the ext4.git changes for the next merge
window), I'm seeing very similar failures on commit 50987beca096
("Merge tag 'trace-v5.12-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace")
See attached makelog and config.gz.
Fortunately the configs used by kunit tests don't seem to technical
the issue. So it's not something I'm going to care about, but perhaps
it's something the ARCH=um folks might want to address?
- Ted
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 10991 bytes --]
[-- Attachment #3: makelog.gz --]
[-- Type: application/gzip, Size: 21792 bytes --]
prev parent reply other threads:[~2021-04-14 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 13:30 [ext4:dev 13/28] mballoc.c:undefined reference to `atomic64_inc_386' kernel test robot
2021-04-14 20:20 ` Theodore Ts'o [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=YHdOlVdIfeqt7mJQ@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=harshadshirwadkar@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lkp@intel.com \
--cc=ritesh.list@gmail.com \
/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).