All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/9] uclibc-ng: Bump up to 1.0.12 release
Date: Wed, 10 Feb 2016 13:52:44 -0800	[thread overview]
Message-ID: <56BBB12C.3070701@gmail.com> (raw)
In-Reply-To: <850e86b808fa51352203ff92c894eebbb045902a.1455126045.git.raj.khem@gmail.com>

This update includes CVE-2016-2224 and CVE-2016-2225

- armin

On 02/10/2016 09:43 AM, Khem Raj wrote:
> Here are changes between 1.0.11 and 1.0.12
> 
> release 1.0.12 - Chimay Brune
> 
> Leonid Lisovskiy (5):
>      libdl: dlopen() mustn't forget RTLD_NODELETE flag
>      tests: Extend OMIT LDFLAGS logic to test binaries too
>      Provide __adjtimex() alias, like glibc.
>      ldso: Fix fail of $ORIGIN expansion in case of RTLD_NOLOAD
>      ldso: Use single rtld_flags interpretation through all the calls
> 
> Waldemar Brodkorb (11):
>      Suppress warning "_GNU_SOURCE" redefined
>      hppa: unbreak toolchain building
>      test: disable tests requiring math headers
>      nios2: allow to build toolchain
>      add exp10() from glibc
>      Do not follow compressed items forever. <<<<---- CVE-2016-2224
>      Make sure to always terminate decoded string <<<<---- CVE-2016-2225
>      add $ORIGIN test-case
>      mips64: fix memcpy, patch from glibc
>      mips: fix clashing symbols
>      bump version for release
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>  meta/recipes-core/uclibc/uclibc-git.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-core/uclibc/uclibc-git.inc b/meta/recipes-core/uclibc/uclibc-git.inc
> index 490dfcb..0509a6c 100644
> --- a/meta/recipes-core/uclibc/uclibc-git.inc
> +++ b/meta/recipes-core/uclibc/uclibc-git.inc
> @@ -1,6 +1,6 @@
> -SRCREV = "94493929f674f4410c2743fa3dd82fd37b70c58f"
> +SRCREV = "003b266cbeb370a8eae91dc256197f00798c6f93"
>  
> -PV = "1.0.11+git${SRCPV}"
> +PV = "1.0.12+git${SRCPV}"
>  
>  FILESEXTRAPATHS =. "${FILE_DIRNAME}/uclibc-git:"
>  
> 


  reply	other threads:[~2016-02-10 21:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 17:43 [PATCH 0/9] Upgrade uclibc/musl to latest Khem Raj
2016-02-10 17:43 ` [PATCH 1/9] distutils: Consider S != B case Khem Raj
2016-02-10 18:29   ` Richard Purdie
2016-02-10 18:53     ` Khem Raj
2016-02-10 18:54   ` Phil Blundell
2016-02-10 19:01     ` Khem Raj
2016-02-10 17:43 ` [PATCH 2/9] ltp: Upgrade to 20160126 and fix build on musl Khem Raj
2016-02-11 10:12   ` Richard Purdie
2016-02-11 16:13     ` Khem Raj
2016-02-10 17:43 ` [PATCH 3/9] musl: Upgrade to tip of tree Khem Raj
2016-02-10 17:43 ` [PATCH 4/9] uclibc-ng: Bump up to 1.0.12 release Khem Raj
2016-02-10 21:52   ` akuster808 [this message]
2016-02-10 17:43 ` [PATCH 5/9] uclibc: fetch from master branch not 1.0 Khem Raj
2016-02-10 17:43 ` [PATCH 6/9] strace: build fix for MIPS + musl libc Khem Raj
2016-02-10 17:43 ` [PATCH 7/9] gdb: " Khem Raj
2016-02-10 17:43 ` [PATCH 8/9] gdb: drop unnecessary CC_FOR_BUILD etc exports Khem Raj
2016-02-10 17:43 ` [PATCH 9/9] nettle.inc: drop duplicate LIC_FILES_CHKSUM and SRC_URI hashes Khem Raj
2016-02-13  8:23 ` [PATCH 0/9] Upgrade uclibc/musl to latest Richard Purdie
2016-02-13 15:43   ` Khem Raj

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=56BBB12C.3070701@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.