All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Sakib Sajal <sakib.sajal@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: update glibc to HEAD of release/2.34/master to include fix for CVE-2021-38604?
Date: Wed, 18 Aug 2021 15:02:15 -0700	[thread overview]
Message-ID: <CAMKF1spD_gnPW7x5st-5i8VC2wpLmOFGKF9K0iKSSSR4xB=wbw@mail.gmail.com> (raw)
In-Reply-To: <536e91b5-6c16-aeb2-f534-edde8601ac84@windriver.com>

On Wed, Aug 18, 2021 at 2:40 PM Sakib Sajal <sakib.sajal@windriver.com> wrote:
>
> Hi Khem,
>
> I was going to apply the commit
>
> glibc is currently at ae37d06c7d127817ba43850f0f898b793d42aea7, 8
> commits behind origin/release/2.34/master as shown below.
>
> Those commits also contain the fix for CVE-2021-38604. Should I go ahead
> and update:
>
> ./glibc-version.inc:SRCREV_glibc ?=
> "ae37d06c7d127817ba43850f0f898b793d42aea7"
>
> or is there work in progress to do this?

Please go ahead, also add the below information to git commit log.

>
> glibc.git$ git log --oneline ae37d06c7d127817ba43850f0f898b793d42aea7...
> 7c987a5ccb (HEAD, origin/release/2.34/master) librt: add test (bug 28213)
> 7947430322 librt: fix NULL pointer dereference (bug 28213)
> 31902ae639 Linux: Fix fcntl, ioctl, prctl redirects for _TIME_BITS=64
> (bug 28182)
> 9995d0588f iconv_charmap: Close output file when done
> 7ff4da3dc2 copy_and_spawn_sgid: Avoid double calls to close()
> a5bd2e10e0 gaiconf_init: Avoid double-free in label and precedence lists
> 3a48da47a9 gconv_parseconfdir: Fix memory leak
> 0b03996304 ldconfig: avoid leak on empty paths in config file
>
>
> Sakib Sajal
>

  reply	other threads:[~2021-08-18 22:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 21:25 update glibc to HEAD of release/2.34/master to include fix for CVE-2021-38604? Sakib Sajal
2021-08-18 22:02 ` Khem Raj [this message]
2021-08-20  4:08   ` [OE-core] " Armin Kuster

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='CAMKF1spD_gnPW7x5st-5i8VC2wpLmOFGKF9K0iKSSSR4xB=wbw@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sakib.sajal@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.