linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Stuart Yoder <stuart.yoder@arm.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	lenb@kernel.org, rafael@kernel.org, jgg@ziepe.ca,
	peterhuewe@gmx.de, sudeep.holla@arm.com,
	linux-integrity@vger.kernel.org,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: Build error on -next due to tpm_crb.c changes? (was: Re: [PATCH v6 0/5] Add support for the TPM FF-A start method)
Date: Wed, 12 Mar 2025 08:00:55 +0200	[thread overview]
Message-ID: <Z9EjF-pybmZlnTws@kernel.org> (raw)
In-Reply-To: <0ad035ff-400e-4b15-8b8f-40b69152ec46@leemhuis.info>

On Tue, Mar 11, 2025 at 04:21:38PM +0100, Thorsten Leemhuis wrote:
> On 05.03.25 18:36, Stuart Yoder wrote:
> > Firmware Framework for Arm A-profile (FF-A) is a messaging framework
> > for Arm-based systems, and in the context of the TPM CRB driver is used
> > to signal 'start' to a CRB-based TPM service which is hosted in an
> > FF-A secure partition running in TrustZone.
> > 
> > These patches add support for the CRB FF-A start method defined
> > in the TCG ACPI specification v1.4 and the FF-A ABI defined
> > in the Arm TPM Service CRB over FF-A (DEN0138) specification:
> > https://developer.arm.com/documentation/den0138/latest/
> > [...]
> > Stuart Yoder (5):
> >   tpm_crb: implement driver compliant to CRB over FF-A
> >   tpm_crb: clean-up and refactor check for idle support
> >   ACPICA: add start method for Arm FF-A
> >   tpm_crb: add support for the Arm FF-A start method
> >   Documentation: tpm: add documentation for the CRB FF-A interface
> > 
> >  Documentation/security/tpm/tpm_ffa_crb.rst |  65 ++++
> >  drivers/char/tpm/Kconfig                   |   9 +
> >  drivers/char/tpm/Makefile                  |   1 +
> >  drivers/char/tpm/tpm_crb.c                 | 105 +++++--
> >  drivers/char/tpm/tpm_crb_ffa.c             | 348 +++++++++++++++++++++
> >  drivers/char/tpm/tpm_crb_ffa.h             |  25 ++
> >  include/acpi/actbl3.h                      |   1 +
> > [...]
> 
> My daily linux-next builds for Fedora failed building on ARM64 today. I did
> not bisect, but from the error message I suspect it's du to  patches in this
> series touching drivers/char/tpm/tpm_crb.c :
> 
> ld: Unexpected GOT/PLT entries detected!
> ld: Unexpected run-time procedure linkages detected!
> ld: drivers/char/tpm/tpm_crb.o: in function `crb_cancel':
> /builddir/foo//drivers/char/tpm/tpm_crb.c:496:(.text+0x2c0): undefined reference to `tpm_crb_ffa_start'
> ld: drivers/char/tpm/tpm_crb.o: in function `__crb_request_locality':
> /builddir/foo/drivers/char/tpm/tpm_crb.c:285:(.text+0x768): undefined reference to `tpm_crb_ffa_start'
> ld: drivers/char/tpm/tpm_crb.o: in function `__crb_relinquish_locality':
> /builddir/foo/drivers/char/tpm/tpm_crb.c:319:(.text+0x81c): undefined reference to `tpm_crb_ffa_start'
> ld: drivers/char/tpm/tpm_crb.o: in function `__crb_request_locality':
> /builddir/foo/drivers/char/tpm/tpm_crb.c:285:(.text+0x8bc): undefined reference to `tpm_crb_ffa_start'
> ld: drivers/char/tpm/tpm_crb.o: in function `__crb_relinquish_locality':
> /builddir/foo/drivers/char/tpm/tpm_crb.c:319:(.text+0x958): undefined reference to `tpm_crb_ffa_start'
> ld: drivers/char/tpm/tpm_crb.o:/builddir/foo/drivers/char/tpm/tpm_crb.c:474: more undefined references to `tpm_crb_ffa_start' follow
> ld: drivers/char/tpm/tpm_crb.o: in function `crb_acpi_add':
> /builddir/foo/drivers/char/tpm/tpm_crb.c:830:(.text+0x1518): undefined reference to `tpm_crb_ffa_init'
> make[2]: *** [scripts/Makefile.vmlinux:77: vmlinux] Error 1
> make[1]: *** [/builddir/foo/Makefile:1242: vmlinux] Error 2
> make: *** [Makefile:259: __sub-make] Error 2
> 
> Full log:
> https://download.copr.fedorainfracloud.org/results/@kernel-vanilla/next/fedora-41-aarch64/08750241-next-next-all/builder-live.log.gz
> 
> Same problem on Fedora 40, 42 and 43. 

I dropped these commit, requested for fixes from the author, and a
couple of additional nitpicks:

https://lore.kernel.org/all/Z9EiRDuWfPOkcjXN@kernel.org/

BR, Jarkko

      parent reply	other threads:[~2025-03-12  6:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250305173611.74548-1-stuart.yoder@arm.com>
2025-03-11 15:21 ` Build error on -next due to tpm_crb.c changes? (was: Re: [PATCH v6 0/5] Add support for the TPM FF-A start method) Thorsten Leemhuis
2025-03-11 15:53   ` Build error on -next due to tpm_crb.c changes? Stuart Yoder
2025-03-11 16:51     ` Thorsten Leemhuis
2025-03-11 18:25       ` Stuart Yoder
2025-03-11 21:17         ` Sudeep Holla
2025-03-12 20:47           ` Stuart Yoder
2025-03-12  2:51       ` Stuart Yoder
2025-03-12  6:48         ` Thorsten Leemhuis
2025-03-12  6:05       ` Jarkko Sakkinen
2025-03-12  6:00   ` Jarkko Sakkinen [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=Z9EjF-pybmZlnTws@kernel.org \
    --to=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=peterhuewe@gmx.de \
    --cc=rafael@kernel.org \
    --cc=stuart.yoder@arm.com \
    --cc=sudeep.holla@arm.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).