From: Jeff Layton <jlayton@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Fwd: [jlayton:mgtime 5/13] inode.c:undefined reference to `__invalid_cmpxchg_size'
Date: Tue, 09 Jul 2024 07:58:03 -0400 [thread overview]
Message-ID: <c1d4fcee3098a58625bb03c8461b92af02d93d15.camel@kernel.org> (raw)
In-Reply-To: 202407091931.mztaeJHw-lkp@intel.com
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
I've been getting some of these warning emails from the KTR. I think
this is in reference to this patch, which adds a 64-bit try_cmpxchg in
the timestamp handling code:
https://lore.kernel.org/linux-fsdevel/20240708-mgtime-v4-0-a0f3c6fb57f3@kernel.org/
On m68k, there is a prototype for __invalid_cmpxchg_size, but no actual
function, AFAICT. Should that be defined somewhere, or is this a
deliberate way to force a build break in this case?
More to the point though: do I need to do anything special for m86k
here (or for other arches that can't do a native 64-bit cmpxchg)?
Thanks,
--
Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: Forwarded message — [jlayton:mgtime 5/13] inode.c:undefined reference to `__invalid_cmpxchg_size' --]
[-- Type: message/rfc822, Size: 6453 bytes --]
From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jlayton:mgtime 5/13] inode.c:undefined reference to `__invalid_cmpxchg_size'
Date: Tue, 9 Jul 2024 19:40:55 +0800
Message-ID: <202407091931.mztaeJHw-lkp@intel.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git mgtime
head: 81b2439edd7c9f966afcb091f414b7f219cda8f6
commit: 2265b64634f4af479ffb0c478409cfd56ec6dc4d [5/13] fs: add infrastructure for multigrain timestamps
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20240709/202407091931.mztaeJHw-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240709/202407091931.mztaeJHw-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/202407091931.mztaeJHw-lkp@intel.com/
All errors (new ones prefixed by >>):
m68k-linux-ld: fs/inode.o: in function `inode_set_ctime_current':
>> inode.c:(.text+0x167a): undefined reference to `__invalid_cmpxchg_size'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2024-07-09 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202407091931.mztaeJHw-lkp@intel.com>
2024-07-09 11:58 ` Jeff Layton [this message]
2024-07-09 13:45 ` [jlayton:mgtime 5/13] inode.c:undefined reference to `__invalid_cmpxchg_size' Geert Uytterhoeven
2024-07-09 14:16 ` Arnd Bergmann
2024-07-09 14:23 ` Jeff Layton
2024-07-09 15:07 ` Arnd Bergmann
2024-07-09 15:27 ` Jeff Layton
2024-07-09 17:06 ` Arnd Bergmann
2024-07-09 18:27 ` Jeff Layton
2024-07-10 8:38 ` Arnd Bergmann
2024-07-10 11:57 ` Jeff Layton
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=c1d4fcee3098a58625bb03c8461b92af02d93d15.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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;
as well as URLs for NNTP newsgroup(s).