All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] brotli: update to version 1.0.7
Date: Tue, 13 Nov 2018 23:47:49 +0100	[thread overview]
Message-ID: <87wopgy4q2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <874ld95464.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Fri, 26 Oct 2018 13:38:11 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

>>>>> "Adrian" == Adrian Perez de Castro <aperez@igalia.com> writes:
 >> On Fri, 26 Oct 2018 12:01:21 +0200, Peter Korsgaard <peter@korsgaard.com> wrote:
 >>> >>>>> "Adrian" == Adrian Perez de Castro <aperez@igalia.com> writes:
 >>> 
 >>> > The new version, among other changes, includes important fixes
 >>> > for unaligned memory access on ARM (both for 32 and 64-bit), as well
 >>> > as performance improvements and build fixes.
 >>> 
 >>> Does this mean that we should backport this version bump to the current
 >>> LTS release (2018.02.x) as well then?

 >> This is probably a good idea. I was reluctant to suggest it from the get-go
 >> because there is no mention to security updates in the release notes, but
 >> the unaligned memory access will cause crashes, which on could argue can be
 >> exploited for DoS attacks ?. Also, it's a point release so the API/ABI of
 >> the library remains the same, and the risk of breaking things is minimal.

 >> So yes, I think it's a good idea to backport the update to the LTS version.

 > Ok, thanks - I'll cherry pick it next time I sync LTS with master.

Committed to 2018.02.x and 2018.08.x, thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2018-11-13 22:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 23:38 [Buildroot] [PATCH 1/1] brotli: update to version 1.0.7 Adrian Perez de Castro
2018-10-26 10:01 ` Peter Korsgaard
2018-10-26 11:14   ` Adrian Perez de Castro
2018-10-26 11:38     ` Peter Korsgaard
2018-11-13 22:47       ` Peter Korsgaard [this message]

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=87wopgy4q2.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 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.