Messages in this thread | | | From | David Howells <> | Subject | Re: 'make O=' indigestion with module signing | Date | Thu, 11 Mar 2021 12:04:19 +0000 |
| |
Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
> So there's something weird going on with scripts/extract-cert when running > as a userid other than the owner of the source tree.. I wonder if it's > actually an OpenSSL issue...
I cloned next-20210311 as one user then built it as another user using:
LANG=C nice -19 make O=/data/git/next-20210311-build -j8 allmodconfig LANG=C nice -19 make O=/data/git/next-20210311-build -j8
It built with no problems. The building user definitely can't create/modify files in the source directory.
Interestingly, the following line in the output from mine:
EXTRACT_CERTS certs/signing_key.pem
doesn't show the full path as it does in yours:
EXTRACT_CERTS /usr/src/linux-next/"certs/signing_key.pem"
but I don't know why. There are some odd quotes in your line also which may be related to the problem. The relevant config line looks the same:
CONFIG_MODULE_SIG_KEY="certs/signing_key.pem"
I'll have to try with the aarch64 build, see if it's something in that that's the problem.
David
| |