public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: steve@sakoman.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][kirkstone 10/10] glibc: Add single-threaded fast path to rand()
Date: Thu, 10 Apr 2025 12:33:42 +0100	[thread overview]
Message-ID: <3a3917e7e0b9c3f444ee895f24ca401b36e6c694.camel@linuxfoundation.org> (raw)
In-Reply-To: <19fcc012160c6b8782be0e6fc54797c88bf084ba.1744145328.git.steve@sakoman.com>

On Tue, 2025-04-08 at 13:51 -0700, Steve Sakoman via
lists.openembedded.org wrote:
> From: Haixiao Yan <haixiao.yan.cn@windriver.com>
> 
> Backport a patch [1] to improve performance of rand() and
> __random()[2]
> by adding a single-threaded fast path.
> 
> [1]
> https://sourceware.org/git/?p=glibc.git;a=commit;h=be0cfd848d9ad7378800d6302bc11467cf2b514f
> [2] https://sourceware.org/bugzilla/show_bug.cgi?id=32777
> Signed-off-by: Haixiao Yan <haixiao.yan.cn@windriver.com>
> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> ---
>  ...dd-single-threaded-fast-path-to-rand.patch | 47
> +++++++++++++++++++
>  meta/recipes-core/glibc/glibc_2.35.bb         |  1 +
>  2 files changed, 48 insertions(+)
>  create mode 100644 meta/recipes-core/glibc/glibc/0001-stdlib-Add-
> single-threaded-fast-path-to-rand.patch

This isn't in walnascar yet.

Cheers,

Richard


  reply	other threads:[~2025-04-10 11:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 20:50 [OE-core][kirkstone 00/10] Patch review Steve Sakoman
2025-04-08 20:50 ` [OE-core][kirkstone 01/10] curl: ignore CVE-2025-0725 Steve Sakoman
2025-04-08 20:50 ` [OE-core][kirkstone 02/10] ofono: patch CVE-2024-7537 Steve Sakoman
2025-04-08 20:50 ` [OE-core][kirkstone 03/10] ghostscript: Fix CVE-2025-27830 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 04/10] ghostscript: Fix CVE-2025-27831 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 05/10] ghostscript: Fix CVE-2025-27832 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 06/10] ghostscript: Fix CVE-2025-27834 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 07/10] ghostscript: Fix CVE-2025-27835 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 08/10] ghostscript: Fix CVE-2025-27836 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 09/10] qemu: ignore CVE-2023-1386 Steve Sakoman
2025-04-10 11:32   ` Richard Purdie
2025-04-08 20:51 ` [OE-core][kirkstone 10/10] glibc: Add single-threaded fast path to rand() Steve Sakoman
2025-04-10 11:33   ` Richard Purdie [this message]
2025-04-10 13:49     ` Steve Sakoman
2025-04-10 15:30       ` Randy MacLeod

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=3a3917e7e0b9c3f444ee895f24ca401b36e6c694.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.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