Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Sender: Valdis Kletnieks <valdis@vt.edu>
From:   "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <valdis.kletnieks@vt.edu>
To:     David Howells <dhowells@redhat.com>
Cc:     David Woodhouse <dwmw2@infradead.org>, keyrings@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: 'make O=' indigestion with module signing
In-Reply-To: <860945.1615455241@warthog.procyon.org.uk>
References: <91190.1615444370@turing-police>
 <860945.1615455241@warthog.procyon.org.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1615456309_76436P";
         micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date:   Thu, 11 Mar 2021 04:51:49 -0500
Message-ID: <102790.1615456309@turing-police>
Precedence: bulk

--==_Exmh_1615456309_76436P
Content-Type: text/plain; charset=us-ascii

On Thu, 11 Mar 2021 09:34:01 +0000, David Howells said:
> Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
>
> > What i *expected* was that multiple builds with different O= would each
> > generate themselves a unique signing key and put it in their own O= directory
> > and stay out of each other's way.
>
> Hmmm...  Works for me.  I use separate build dirs all the time.
>
> What version of the kernel are you using and what's the build command line -
> in particular the full O= option?

This is linux-next as of yesterday. For testing, I've been using:

LANG=C make O=/tmp/arm64 V=1 ARCH=arm64 ASFLAGS='-mcpu=all' CROSS_COMPILE=/opt/aarch64/bin/aarch64-linux-gnu- certs/

and it insists on trying to make the certs in /usr/src/linux-next rather than /tmp/arm64:

make -f /usr/src/linux-next/scripts/Makefile.build obj=certs \
single-build= \
need-builtin=1 need-modorder=1
  scripts/extract-cert /usr/src/linux-next/"certs/signing_key.pem" certs/signing_key.x509
At main.c:142:
- SSL error:0200100D:system library:fopen:Permission denied: ../crypto/bio/bss_file.c:69
- SSL error:2006D002:BIO routines:BIO_new_file:system lib: ../crypto/bio/bss_file.c:78
extract-cert: /usr/src/linux-next/certs/signing_key.pem: Permission denied
make[2]: *** [/usr/src/linux-next/certs/Makefile:106: certs/signing_key.x509] Error 1
make[1]: *** [/usr/src/linux-next/Makefile:1847: certs] Error 2
make[1]: Leaving directory '/tmp/arm64'
make: *** [Makefile:215: __sub-make] Error 2


Is it possible that it works for you because although you have
separate build dirs, it's still able to write to the source tree?


--==_Exmh_1615456309_76436P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Comment: Exmh version 2.9.0 11/07/2018

iQIVAwUBYEnoNQdmEQWDXROgAQIeahAAk0hEOVyD2An8GEIm/htx8n04cbX8WF7O
j8OZk+N5OHOZ1RI/ORTvZiNDfz/tNjSv6W4ELTe481ozAs3N8syGNzTbKi4m615Q
9OLHfw5EwOc/KMydbedZveB1kS2y03dsBnsZU/lnuHQq4mPvnyvWIv5rEUIXtRf9
SGXxl1vIVxuBasmn30C8fShhDWf6W9dtGIGynQs7dhOOpFOpqh4Vyb/VYiRDVDCy
r/1LLQXgUgPIbcJSvAeOucte6wENNmEtYpf16T1vJZ0eoUK7MymD71Xhv/i48o2C
lDmflllLJb1XLGKeHC04Jp5jTsmvdcmmynjAhiU6pvziFMyas7JKbK3isS8B00JC
NvLk+f4v1g4CkG5ExryQe7Z9+pqVoUAQri+AmPFAUvALNycqJojOTxH3QOeZ+D/T
CMuSKeQoswcJm1BE/FmvyaGPzpwL7eS3YjZ5cV2Gi8Wz+kQVtQpakuIvH1TNnWC3
1qrsB1pyfe69uTfrtmdpaVTiQ+g1QtzDnWpbmSmrgUXvvhBmB3upjMQAQNG6KDqs
YVEG4eaIsSjsxV9lGyut2acbpgC/jR8EYSIrIH5Xl/UdI+FxhYQZ3rHg7gJknazv
GeYgcs1pB56dPEuTH281eVxD4goqZH6UA01gEj3MeXs8xWnVs0sXiq47pYEPGjmV
I3L/oA3HRXQ=
=b6qj
-----END PGP SIGNATURE-----

--==_Exmh_1615456309_76436P--