From: Tom Rini <trini@konsulko.com>
To: Michal Simek <michal.simek@amd.com>
Cc: u-boot@lists.denx.de, git@xilinx.com,
Oleksandr Suvorov <oleksandr.suvorov@foundries.io>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 0/4] zlib: Address CVE-2016-9841
Date: Thu, 28 Mar 2024 16:02:03 -0400 [thread overview]
Message-ID: <20240328200203.GD3442575@bill-the-cat> (raw)
In-Reply-To: <cover.1711548887.git.michal.simek@amd.com>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
On Wed, Mar 27, 2024 at 03:14:49PM +0100, Michal Simek wrote:
> Hi,
>
> it looks like that only CVE-2016-9841 is not fixed and this series is
> trying to address it. The first two patches are just preparation based on
> changes which happened in past. The third one is actual fix and the last
> one is following what has been done in Linux kernel long time ago and don't
> use incorrect zlib version string.
>
> I tested it with and I can't see any issue.
> ./test/py/test.py --bd sandbox --build -s
>
> And gitlab CI is also not showing any issue.
Thanks for taking this on. I've given it a quick spin on some Pi
platforms as well as before/after and I see that it's also reducing the
overall binary size everywhere as well.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-03-28 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 14:14 [PATCH 0/4] zlib: Address CVE-2016-9841 Michal Simek
2024-03-27 14:14 ` [PATCH 1/4] zlib: Rename this variable to here (current decoding table entry) Michal Simek
2024-03-27 14:14 ` [PATCH 2/4] zlib: Rename write variable to wnext (window write index) Michal Simek
2024-03-27 14:14 ` [PATCH 3/4] zlib: Port fix for CVE-2016-9841 to U-Boot Michal Simek
2024-03-27 14:14 ` [PATCH 4/4] zlib: Remove incorrect ZLIB_VERSION Michal Simek
2024-03-28 20:02 ` Tom Rini [this message]
2024-04-12 21:59 ` [PATCH 0/4] zlib: Address CVE-2016-9841 Tom Rini
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=20240328200203.GD3442575@bill-the-cat \
--to=trini@konsulko.com \
--cc=git@xilinx.com \
--cc=michal.simek@amd.com \
--cc=oleksandr.suvorov@foundries.io \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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