From: Eric Biggers <ebiggers@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
oe-kbuild-all@lists.linux.dev, Ard Biesheuvel <ardb@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [ebiggers:sha256-lib-v4 4/13] /tmp/ccoCWqTC.s: Error: local label `"3" (instance number 1 of a fb label)' is not defined
Date: Wed, 7 May 2025 10:13:41 -0700 [thread overview]
Message-ID: <20250507171341.GA181648@sol> (raw)
In-Reply-To: <c4a017e9-0169-4f7a-99a1-7ae1bbee4a19@leemhuis.info>
On Wed, May 07, 2025 at 12:56:22PM +0200, Thorsten Leemhuis wrote:
> [+linux-crypto and +Herbert Xu, who committed that change that showed up
> in -next today; sorry for forgetting this earlier]
>
> On 07.05.25 12:50, Thorsten Leemhuis wrote:
> > On 07.05.25 12:25, kernel test robot wrote:
> >> tree: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git sha256-lib-v4
> >> head: 849682242c36727c23430b6cfed12e4422313931
> >> commit: 9f2dd94847c914bb716be744e12cb02f175638db [4/13] crypto: arm64/sha256 - implement library instead of shash
> >> config: arm64-randconfig-003-20250429 (https://download.01.org/0day-ci/archive/20250507/202505071811.yYpLUbav-lkp@intel.com/config)
> >> compiler: aarch64-linux-gcc (GCC) 9.5.0
> >> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250507/202505071811.yYpLUbav-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/202505071811.yYpLUbav-lkp@intel.com/
> >>
> >> All errors (new ones prefixed by >>):
> >>
> >> /tmp/ccoCWqTC.s: Assembler messages:
> >>>> /tmp/ccoCWqTC.s: Error: local label `"3" (instance number 1 of a fb label)' is not defined
> >
> > I ran into the same problem today when building -next rpms for arm64
> > Fedora using the approach and configuration used to build the kernel
> > rpms shipped in Fedora rawhide.
> >
> > Full build log:
> >
> > https://download.copr.fedorainfracloud.org/results/@kernel-vanilla/next/fedora-rawhide-aarch64/09006679-next-next-all/builder-live.log.gz
> >
> > Ciao, Thorsten
Thanks. https://lore.kernel.org/r/20250507170901.151548-1-ebiggers@kernel.org
fixes this. This was specific to CONFIG_PREEMPT_VOLUNTARY=y, which I've now
added to the lists of configs I test...
- Eric
prev parent reply other threads:[~2025-05-07 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202505071811.yYpLUbav-lkp@intel.com>
2025-05-07 10:50 ` [ebiggers:sha256-lib-v4 4/13] /tmp/ccoCWqTC.s: Error: local label `"3" (instance number 1 of a fb label)' is not defined Thorsten Leemhuis
2025-05-07 10:56 ` Thorsten Leemhuis
2025-05-07 17:13 ` Eric Biggers [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=20250507171341.GA181648@sol \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@leemhuis.info \
--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