Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2C39AC6FD19 for ; Thu, 16 Mar 2023 08:47:46 +0000 (UTC) Received: from mail-wm1-f45.google.com (mail-wm1-f45.google.com [209.85.128.45]) by mx.groups.io with SMTP id smtpd.web11.7729.1678956456800161649 for ; Thu, 16 Mar 2023 01:47:37 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@linuxfoundation.org header.s=google header.b=UBCRJ17j; spf=pass (domain: linuxfoundation.org, ip: 209.85.128.45, mailfrom: richard.purdie@linuxfoundation.org) Received: by mail-wm1-f45.google.com with SMTP id bg16-20020a05600c3c9000b003eb34e21bdfso2645107wmb.0 for ; Thu, 16 Mar 2023 01:47:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1678956455; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=o1iE0+tOR5OYU0qSvdAS0UxjE0N1J+AYrEyUSJBYcjs=; b=UBCRJ17jV3RKLvATMJvtO+HD5q/zx2wsfvE13dK6+KEXSCt7OWhdJlEMWhrIOCgGyE JXdgrtHd/Cf32ykYCbb6LRtoWiz01klAleJMQ5FPP0UbKBX5TZBbYGenCIFqvEUqRTje MfpiBTNJkFPf4Q7evANrhNzqWg1jFLaTnP9As= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678956455; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=o1iE0+tOR5OYU0qSvdAS0UxjE0N1J+AYrEyUSJBYcjs=; b=QW8Qaukwk5ghdCkLnlJuFYh167dmJTJsAtDWLpQg9P5FlG2Dtm2RqwPQ/FXH0Ezr8v /g53wG74/OJmrpyWqnf4runPL6+TdcV/dR1H2M/dYu/TEtYCOVg3B850cWxAcKHFT1+h dfyQnFyjEr782yD0oAwxyr2q8haXe7zpWa57DJw+/HcSwMjRm+Fdsrk2ccyN5d6Ao3SD lSp4rA7DC1phIymhGZ0sH/6sCRrjbm8v5T7rJCFJVuk+lQKog7i7UPe2LQZp93BEFgZH 7lgKrXa1p4xsfEyLP2FAAaZYZB0HTBu7YEj1mQV0rqHz+Pw+6DadonqYY1IYUJTCHurk nyTw== X-Gm-Message-State: AO0yUKUrA6cm+uC4rkJsWkKjuxEHtF8VcKe69kKXfuH3QCHSaVG0uzaF IQ1FbRUEnSZ4u2YoJE4QDovmOQ== X-Google-Smtp-Source: AK7set88XJ7mf3HrCVyXu4l5XJF8awBTHbIDeTQuLHOtMZ5HRuY39T/NbMclMVU1dB/cbjrGqQEScw== X-Received: by 2002:a05:600c:190c:b0:3eb:38e6:f65d with SMTP id j12-20020a05600c190c00b003eb38e6f65dmr20488643wmq.11.1678956455239; Thu, 16 Mar 2023 01:47:35 -0700 (PDT) Received: from ?IPv6:2001:8b0:aba:5f3c:4181:67:6e43:6a9? ([2001:8b0:aba:5f3c:4181:67:6e43:6a9]) by smtp.gmail.com with ESMTPSA id iz11-20020a05600c554b00b003ed201ddef2sm4411850wmb.2.2023.03.16.01.47.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Mar 2023 01:47:34 -0700 (PDT) Message-ID: <3d06ea7633a5ddb64833cc3cc35220f6b60cc6a2.camel@linuxfoundation.org> Subject: Re: [OE-core] [PATCH] openssl: update from 3.0.8 to 3.1.0 From: Richard Purdie To: Alexander Kanavin Cc: Randy MacLeod , openembedded-core@lists.openembedded.org Date: Thu, 16 Mar 2023 08:47:34 +0000 In-Reply-To: References: <174C7E5950269FC6.10695@lists.openembedded.org> <174C7EF34675A6EF.8829@lists.openembedded.org> <174C9C60B65DBC68.8829@lists.openembedded.org> <7b2609b8-5834-1639-3885-388e3f9c3cc2@windriver.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.3-1 MIME-Version: 1.0 List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Thu, 16 Mar 2023 08:47:46 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/178685 On Thu, 2023-03-16 at 09:36 +0100, Alexander Kanavin wrote: > On Thu, 16 Mar 2023 at 09:30, Richard Purdie > wrote: > > In the openssl source this is generated by a perl script, > > rypto/modes/asm/aes-gcm-avx512.pl > >=20 > > Wearing suitable safety equipment to stop it burning, inside the perl > > script you can see references like: > >=20 > > my $rndsuffix =3D &random_string(); > >=20 > > I think this is done to avoid symbol clashes but I couldn't see > > anything that would actually clash so more understanding of that this > > is doing is needed. I wondered if we could set some kind of perl > > seeding to make it deterministic. > >=20 > > I'll reply again if I learn anything more. >=20 > Even if it's not a real fix, avx-512 support can be more or less > disabled by default, as support for that is limited to high end server > grade chips. We haven't enabled avx/avx2 yet :) I think the fix might be straight forward and just to add something like: # Ensure the local labels are reproduicble srand(10000); I'll put that into testing, see how it looks. Cheers, Richard