From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrian Perez de Castro Date: Fri, 26 Oct 2018 14:14:25 +0300 Subject: [Buildroot] [PATCH 1/1] brotli: update to version 1.0.7 In-Reply-To: <87h8h958ni.fsf@dell.be.48ers.dk> References: <20181024233823.22831-1-aperez@igalia.com> <87h8h958ni.fsf@dell.be.48ers.dk> Message-ID: <20181026141425.GB4330@momiji> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Fri, 26 Oct 2018 12:01:21 +0200, Peter Korsgaard wrote: > >>>>> "Adrian" == Adrian Perez de Castro 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. > > Patch "0001-Tell-CMake-to-not-check-for-a-C-compiler.patch" is not > > needed due to the issue being fixed upstream, and therefore is removed. > > > Patch "0001-CMake-Allow-using-BUILD_SHARED_LIBS-to-choose-static.patch" > > is rebased against the latest upstream changes. > > > Signed-off-by: Adrian Perez de Castro > > Committed, thanks. \o/ Cheers, -Adri?n -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available URL: