From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io
Cc: "Pedro Falcato" <pedro.falcato@gmail.com>,
"Marvin Häuser" <mhaeuser@posteo.de>,
"Savva Mitrofanov" <savvamtr@gmail.com>
Subject: [PATCH 0/3] Ext4Pkg: Small ext4 fixes and improvements
Date: Wed, 11 Jan 2023 23:59:15 +0000 [thread overview]
Message-ID: <20230111235920.252317-1-pedro.falcato@gmail.com> (raw)
This patch set includes small fixes on Ext4Dxe, including a fix for a (mostly-harmless) out-of-bounds.
Previous versions of these patches were posted standalone before and are now being consolidated into a
patch-set for easier reviewing.
Cc: Marvin Häuser <mhaeuser@posteo.de>
Cc: Savva Mitrofanov <savvamtr@gmail.com>
Pedro Falcato (3):
Ext4Pkg: Fix out-of-bounds read in Ext4ReadDir
Ext4Pkg: Add documentation surrounding ext4 directory entries
Ext4Pkg: Fix and clarify handling regarding non-utf8 dir entries
Features/Ext4Pkg/Ext4Dxe/Directory.c | 49 +++++++++++++++++++++-------
Features/Ext4Pkg/Ext4Dxe/Ext4Disk.h | 21 ++++++++++--
Features/Ext4Pkg/Ext4Dxe/Ext4Dxe.h | 13 ++++----
3 files changed, 62 insertions(+), 21 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-11 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 23:59 Pedro Falcato [this message]
2023-01-11 23:59 ` [PATCH 1/2] Ext4Pkg: Add documentation surrounding ext4 directory entries Pedro Falcato
2023-01-11 23:59 ` [PATCH 1/3] Ext4Pkg: Fix out-of-bounds read in Ext4ReadDir Pedro Falcato
2023-01-14 17:05 ` Marvin Häuser
2023-01-11 23:59 ` [PATCH 2/3] Ext4Pkg: Add documentation surrounding ext4 directory entries Pedro Falcato
2023-01-14 17:10 ` Marvin Häuser
2023-01-11 23:59 ` [PATCH 2/2] Ext4Pkg: Fix and clarify handling regarding non-utf8 dir entries Pedro Falcato
2023-01-11 23:59 ` [PATCH 3/3] " Pedro Falcato
2023-01-14 17:13 ` Marvin Häuser
[not found] ` <1739669F06B92E95.23170@groups.io>
2023-01-12 0:04 ` [edk2-devel] [PATCH 2/3] Ext4Pkg: Add documentation surrounding ext4 directory entries Pedro Falcato
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-list 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=20230111235920.252317-1-pedro.falcato@gmail.com \
--to=devel@edk2.groups.io \
/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