From: Daniel Axtens <dja@axtens.net>
To: grub-devel@gnu.org
Cc: Daniel Axtens <dja@axtens.net>
Subject: [PATCH 0/2] Two small fixes to gzip
Date: Mon, 13 May 2024 00:32:07 +1000 [thread overview]
Message-ID: <20240512143209.44357-1-dja@axtens.net> (raw)
I've been fuzzing gzip a bit. So far nothing super exciting, but it's helpful
to add some code to bail early on EOF (patch 1) and to avoid some uninitialised
data warnings from valgrind (patch 2). I'm not aware of any security implications
of either change, and the gzip compression test still passes.
Daniel Axtens (2):
gzio: abort early when get_byte reads nothing
gzio: Properly init a table
grub-core/io/gzio.c | 55 ++++++++++++++++++++++++++++-----------------
1 file changed, 35 insertions(+), 20 deletions(-)
--
2.39.3 (Apple Git-145)
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2024-05-12 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 14:32 Daniel Axtens [this message]
2024-05-12 14:32 ` [PATCH 1/2] gzio: abort early when get_byte reads nothing Daniel Axtens
2024-05-12 14:32 ` [PATCH 2/2] gzio: Properly init a table Daniel Axtens
2024-05-17 10:29 ` [PATCH 0/2] Two small fixes to gzip Daniel Kiper
2024-05-18 4:52 ` Daniel Axtens
2024-05-20 16:58 ` Daniel Kiper
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=20240512143209.44357-1-dja@axtens.net \
--to=dja@axtens.net \
--cc=grub-devel@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).