update glibc to HEAD of release/2.34/master to include fix for CVE-2021-38604?

update glibc to HEAD of release/2.34/master to include fix for CVE-2021-38604?

[Sakib Sajal]

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?

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

Re: update glibc to HEAD of release/2.34/master to include fix for CVE-2021-38604?

[Khem Raj]

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
>

Re: [OE-core] update glibc to HEAD of release/2.34/master to include fix for CVE-2021-38604?

[Armin Kuster]

On 8/18/21 3:02 PM, Khem Raj wrote:
> 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)
FYI: bug 28213 fixes CVE-2021-38604
>> 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
>>
>>
>> 
>>