Keyrings Archive mirror
 help / color / mirror / Atom feed
From: GONG Ruiqi <gongruiqi1@huawei.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	Roberto Sassu <roberto.sassu@huawei.com>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Eric Snowberg <eric.snowberg@oracle.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	"Lee, Chun-Yi" <jlee@suse.com>, <linuxppc-dev@lists.ozlabs.org>,
	<linux-kernel@vger.kernel.org>, <linux-s390@vger.kernel.org>,
	<linux-integrity@vger.kernel.org>, <keyrings@vger.kernel.org>,
	Lu Jialin <lujialin4@huawei.com>
Subject: Re: [PATCH RESEND] integrity: Extract secure boot enquiry function out of IMA
Date: Sat, 28 Jun 2025 10:37:18 +0800	[thread overview]
Message-ID: <267d0e56-6040-426c-8b1e-a53b18829871@huawei.com> (raw)
In-Reply-To: <aF6/ItTfd7oVN+Sn@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com>



On 2025/06/27 23:56, Alexander Gordeev wrote:
> On Thu, Jun 26, 2025 at 10:36:17AM +0800, GONG Ruiqi wrote:
> 
> Hi GONG,
> 
> ...
>> Compile-tested for powerpc, s390 and x86, all with allmodconfig.
> 
> This breaks defconfig and debug_defconfig builds on s390
> since IMA_ARCH_POLICY=n in these configurations and thus
> CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT=n as well:

Hi Alexander,

Thanks for the feedback! I'll fix it and send a V2 asap.

BR,
Ruiqi

> 
> s390x-15.1.0-ld: security/integrity/ima/ima_main.o: in function `ima_load_data':
> /home/agordeev/linux.c3/security/integrity/ima/ima_main.c:902:(.text+0x54e): undefined reference to `arch_integrity_get_secureboot'
> s390x-15.1.0-ld: security/integrity/ima/ima_appraise.o: in function `ima_appraise_parse_cmdline':
> /home/agordeev/linux.c3/security/integrity/ima/ima_appraise.c:30:(.init.text+0x44): undefined reference to `arch_integrity_get_secureboot'
> make[2]: *** [scripts/Makefile.vmlinux:91: vmlinux.unstripped] Error 1
> make[1]: *** [/home/agordeev/linux.c3/Makefile:1236: vmlinux] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
> 
>> Signed-off-by: GONG Ruiqi <gongruiqi1@huawei.com>
> 
> Thanks!

      reply	other threads:[~2025-06-28  2:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26  2:36 [PATCH RESEND] integrity: Extract secure boot enquiry function out of IMA GONG Ruiqi
2025-06-27 15:56 ` Alexander Gordeev
2025-06-28  2:37   ` GONG Ruiqi [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=267d0e56-6040-426c-8b1e-a53b18829871@huawei.com \
    --to=gongruiqi1@huawei.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=eric.snowberg@oracle.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=jarkko@kernel.org \
    --cc=jlee@suse.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lujialin4@huawei.com \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=roberto.sassu@huawei.com \
    --cc=svens@linux.ibm.com \
    --cc=zohar@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).