Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH=2020.02.x] package/redis: bump version to 5.0.9
Date: Sun, 05 Jul 2020 22:46:43 +0200	[thread overview]
Message-ID: <87zh8d666k.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LWhoLwig3i8FNjC3OQ65h27y50cbu5ROZkBHKnnXsjSUw@mail.gmail.com> (Thomas De Schampheleire's message of "Mon, 29 Jun 2020 12:51:02 +0200")

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:

 > Hello,
 > El lun., 22 jun. 2020 a las 9:49, Titouan Christophe (<
 > titouan.christophe at railnova.eu>) escribi?:

 >> Hello Peter and all,
 >> 
 >> On 21/06/20 23:39, Peter Korsgaard wrote:
 >> > Fixes a critical issue related to streams. From the release notes:
 >> >
 >> >
 >> ================================================================================
 >> > Redis 5.0.9     Released Thu Apr 17 12:41:00 CET 2020
 >> >
 >> ================================================================================
 >> >
 >> > Upgrade urgency:CRITICAL if you use Streams with AOF ore replicas.
 >> >                  Otherwise the upgrade urgency is LOW.
 >> >
 >> > This release has a speed improvement and a critical fix:
 >> >
 >> >      * FIX: XREADGROUP when fetching data in a blocking way, would not
 >> >             emit the XCLAIM in the AOF file and to replicas. This means
 >> >             that the last ID is not updated, and that restarting the
 >> server
 >> >             will have the effect of reprocessing some entries.
 >> >      * NEW: Clients blocked on the same key are now unblocked on
 >> >             O(1) time. Backported from Redis 6.
 >> >
 >> > Commits:
 >> >
 >> >      1fc8ef81a Fix XCLAIM propagation in AOF/replicas for blocking
 >> XREADGROUP.
 >> >      a5e24eabc Speedup: unblock clients on keys in O(1).
 >> >
 >> > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>Acked-by: Titouan
 >> Christophe <titouan.christophe@railnova.eu>
 >> 

 > Just want to highlight that also the 5.0.8 turns out to have a security
 > fix: http://cve.circl.lu/cve/CVE-2020-14147

True. Committed to 2020.02.x and 2020.05.x after adding the CVE info.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2020-07-05 20:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 21:39 [Buildroot] [PATCH=2020.02.x] package/redis: bump version to 5.0.9 Peter Korsgaard
2020-06-22  7:49 ` Titouan Christophe
2020-06-29 10:51   ` Thomas De Schampheleire
2020-06-29 12:07     ` Thomas Petazzoni
2020-06-29 12:16       ` Thomas De Schampheleire
2020-06-29 15:30       ` Titouan Christophe
2020-06-29 18:47         ` Thomas Petazzoni
2020-07-05 20:46     ` Peter Korsgaard [this message]
2020-07-05 20:48       ` Peter Korsgaard
2020-07-06 11:20         ` Thomas De Schampheleire

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=87zh8d666k.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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