| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <c1d4fcee3098a58625bb03c8461b92af02d93d15.camel@kernel.org>
Date: Tue, 09 Jul 2024 07:58:03 -0400
From: Jeff Layton <jlayton@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Fwd: [jlayton:mgtime 5/13] inode.c:undefined reference to
`__invalid_cmpxchg_size'
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@...nel.org>
Delivered-To: jlayton@...chiereds.net
Received: by 2002:a05:6840:a05a:b0:1868:30e0:1b91 with SMTP id
s26csp2141718nlm; Tue, 9 Jul 2024 04:41:32 -0700 (PDT)
X-Forwarded-Encrypted: i=2;
AJvYcCVmB1k3maNpx1LDNc1A91iZlu6jOn1vFp6JYZa0a/MyZJBGCaQOsnxUCSdNL3wuTBZUfnyPVfsvIkwRFSD2AiJbZYr/J8T3gA==
X-Google-Smtp-Source:
AGHT+IGO4p0CRHr1++kSKxppOqzc9unXWajhJMXaYuWUPZIiFaYUeK2qVsj3NggYMRIIpbZ2bGd0
X-Received: by 2002:a17:902:e5c2:b0:1fb:75b6:a40e with SMTP id
d9443c01a7336-1fbb6d601dcmr18995115ad.45.1720525292732; Tue, 09 Jul 2024
04:41:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1720525292; cv=none; d=google.com;
s=arc-20160816;
b=OxDrk1F4jlBzkr4XEJtM25mCkyRvQXZpVI2sqE+amYspGExFlRbhZrd8mh1wQn8Pps
c01F6WIarIgL2QrIGsuA9ThI/wk/fWQ1VgBE0YTGqBbpW13316YYQlxgOL59r1Gup9c0
NRKfB8LAyLLRrD9V2K5xEw3kPH4fPQgDq15goajWPZaWLLDFTCJExE/Fs90jd5wHZ7dl
ogP53L8MsPuov5YXdmNj8/PlSWLEryx2Aq+WzkOmUCoRCvGa5QkHBjYhrz7VIPzTqCpb
Sqsi+h4UMZMc3e3sbbvz/LdFL1f/iz9993+1oDX5+XYx8JCSXMkaAigBhBZ2XZ+oi5bZ +6vQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
s=arc-20160816;
h=content-disposition:mime-version:message-id:subject:cc:to:from:date
:dkim-signature:dmarc-filter:delivered-to;
bh=fp4wInhpYjV2aixZjBcpP8sNJTgUz58P0dXQltVokMs=;
fh=pVpjrWokx+suM3VInIbJAR8sYUQKzjSbDwxWk5bUObQ=;
b=z0CLAn09s+qJcsvQojLxvCX8xMjzqPjGa1VRXn2dxZJA6BgIuuCXViSpBMZyCDHgsX
4d+3/luio8Y4lKwPJZfD1UplNEXWGmfgHH0zhkCMd2YQ0f4jrlpH9eEYSO8nQ1LfgpX7
k4z3iLE4VEu8xAsQ3mXtGfMh8M0xzzulDAHhLAKEjKLZ838Inyf2r6C3Na3Z3ZX4wF6n
AFpYMfXilw5fU7HKfrhL6qD9UnHhgtC3SlYcj/v957QnuDx/0E4iJgG8mVclmKzBhb5K
M7KoHcHhiGscicZKDK1arJ2ks3DXoPLdHWnHF344YNmjDydIuxnXc+RJhnoYtqxxEKs/
vWYQ==; dara=google.com
ARC-Authentication-Results: i=1; mx.google.com; dkim=pass
header.i=@...el.com header.s=Intel header.b=nrrnfaux; spf=pass (google.com:
domain of srs0=yxw6=oj=intel.com=lkp@...nel.org designates 145.40.73.55 as
permitted sender) smtp.mailfrom="SRS0=YXW6=OJ=intel.com=lkp@...nel.org";
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com
Return-Path: <SRS0=YXW6=OJ=intel.com=lkp@...nel.org>
Received: from sin.source.kernel.org (sin.source.kernel.org.
[145.40.73.55]) by mx.google.com with ESMTPS id
d9443c01a7336-1fbb6ad51f1si17765385ad.606.2024.07.09.04.41.32 for
<jlayton@...chiereds.net> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384
bits=256/256); Tue, 09 Jul 2024 04:41:32 -0700 (PDT)
Received-SPF: pass (google.com: domain of
srs0=yxw6=oj=intel.com=lkp@...nel.org designates 145.40.73.55 as permitted
sender) client-ip=145.40.73.55;
Authentication-Results: mx.google.com; dkim=pass header.i=@...el.com
header.s=Intel header.b=nrrnfaux; spf=pass (google.com: domain of
srs0=yxw6=oj=intel.com=lkp@...nel.org designates 145.40.73.55 as permitted
sender) smtp.mailfrom="SRS0=YXW6=OJ=intel.com=lkp@...nel.org"; dmarc=pass
(p=NONE sp=NONE dis=NONE) header.from=intel.com
Received: from smtp.kernel.org (transwarp.subspace.kernel.org
[100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id
5D51BCE1171 for <jlayton@...chiereds.net>; Tue, 9 Jul 2024 11:41:29 +0000
(UTC)
Received: by smtp.kernel.org (Postfix)
id 9AFAAC4AF0A; Tue, 9 Jul 2024 11:41:28 +0000 (UTC)
Delivered-To: jlayton@...nel.org
Received: by smtp.kernel.org (Postfix) with ESMTPS id 1CC7FC4AF0C
for <jlayton@...nel.org>; Tue, 9 Jul 2024 11:41:26 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.4.1 smtp.kernel.org 1CC7FC4AF0C
Authentication-Results: smtp.kernel.org; dmarc=pass (p=none dis=none)
header.from=intel.com
Authentication-Results: smtp.kernel.org; spf=pass smtp.mailfrom=intel.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=intel.com; i=@...el.com; q=dns/txt; s=Intel;
t=1720525287; x=1752061287;
h=date:from:to:cc:subject:message-id:mime-version;
bh=RP32T3RKQMQt+vShPXINsjabD/ZiGWavrgUppvPjLTA=;
b=nrrnfauxz2cLnLs2NivJrNRKBSaCVa1Z1JlTkvmRQx1USrk9LUT4e7h0
6/JBhjatas60/5PwuO1mvjjB0a/t85HH/wF42NEJp+puGQ5dBsyipd9jc
PdbjBK8bpRVCqOBb32dbsY+RI/Aw4Iwg619BqGBCgJJvTArLJKNYWrUTD
Cinqcp/ih8fOMO8iZ7aM3GOAoVtxQCCDnFW5lyFaNUAEShgV3Gx/0kn73
0OtNEnY3qs6QU7YYDScXtMc7YT2myUiutHmlk2XTxKQTHWf+H/LZxzxSU
MeEDbL7KvLIEHnRK2WmRDE7FRfTusoNXPuHK50dHqgK38U1uegud8nlTP
A==;
X-CSE-ConnectionGUID: YaidnIlWRn+StATDhIXh3g==
X-CSE-MsgGUID: 3szOpmabTzG9WoMNNg77Vw==
X-IronPort-AV: E=McAfee;i="6700,10204,11127"; a="17642825"
X-IronPort-AV: E=Sophos;i="6.09,194,1716274800";
d="scan'208";a="17642825"
Received: from fmviesa006.fm.intel.com ([10.60.135.146]) by
fmvoesa111.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Jul
2024 04:41:26 -0700
X-CSE-ConnectionGUID: GjLOCiQoSoSfgSNueGojzQ==
X-CSE-MsgGUID: h6VGuvMzRLao1b8rIoCisQ==
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="6.09,194,1716274800";
d="scan'208";a="47615286"
Received: from lkp-server01.sh.intel.com (HELO 68891e0c336b)
([10.239.97.150]) by fmviesa006.fm.intel.com with ESMTP; 09 Jul 2024
04:41:24 -0700
Received: from kbuild by 68891e0c336b with local (Exim 4.96)
(envelope-from <lkp@...el.com>)
id 1sR9Dm-000Wcp-2s;
Tue, 09 Jul 2024 11:41:22 +0000
Date: Tue, 9 Jul 2024 19:40:55 +0800
From: kernel test robot <lkp@...el.com>
To: Jeff Layton <jlayton@...nel.org>
Cc: oe-kbuild-all@...ts.linux.dev
Subject: [jlayton:mgtime 5/13] inode.c:undefined reference to
`__invalid_cmpxchg_size'
Message-ID: <202407091931.mztaeJHw-lkp@...el.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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@...el.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
Powered by blists - more mailing lists