update glibc to HEAD of release/2.34/master to include fix for CVE-2021-38604?
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 done7ff4da3dc2 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 leak0b03996304 ldconfig: avoid leak on empty paths in config file
Sakib Sajal
Quoted 8 lines · 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.
Quoted 7 lines
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.
Quoted 15 lines
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)31902ae639Linux: Fix fcntl, ioctl, prctl redirects for _TIME_BITS=64 (bug 28182)9995d0588ficonv_charmap: Close output file when done7ff4da3dc2copy_and_spawn_sgid: Avoid double calls toclose()a5bd2e10e0gaiconf_init: Avoid double-free in label and precedence lists3a48da47a9gconv_parseconfdir: Fix memory leak0b03996304ldconfig: avoid leak on empty paths in config fileSakib Sajal
Quoted 8 lines · Khem Raj
Quoted 7 lines · 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.
Quoted 12 lines
Quoted 7 lines
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.
Quoted 3 lines
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
Quoted 14 lines
Quoted 14 lines
31902ae639Linux: Fix fcntl, ioctl, prctl redirects for _TIME_BITS=64 (bug 28182)9995d0588ficonv_charmap: Close output file when done7ff4da3dc2copy_and_spawn_sgid: Avoid double calls toclose()a5bd2e10e0gaiconf_init: Avoid double-free in label and precedence lists3a48da47a9gconv_parseconfdir: Fix memory leak0b03996304ldconfig: avoid leak on empty paths in config fileSakib Sajal