From: "Marvin Häuser" <mhaeuser@posteo.de>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: Savva Mitrofanov <savvamtr@gmail.com>,
edk2-devel-groups-io <devel@edk2.groups.io>,
Vitaly Cheptsov <vit9696@protonmail.com>
Subject: Re: [edk2-platforms][PATCH v3 02/11] Ext4Pkg: Fix incorrect checksum metadata feature check
Date: Mon, 30 Jan 2023 08:38:09 +0000 [thread overview]
Message-ID: <6BC46602-945D-4BB6-80AC-7E2D6ADA420A@posteo.de> (raw)
In-Reply-To: <CAKbZUD2FbxOLzHX1drCO9sJMzypruzDBZm1JZbtVMFgrisXGVg@mail.gmail.com>
With the commit message changed,
Reviewed-by: Marvin Häuser <mhaeuser@posteo.de>
> On 27. Jan 2023, at 15:29, Pedro Falcato <pedro.falcato@gmail.com> wrote:
>
> On Fri, Jan 27, 2023 at 10:02 AM Marvin Häuser <mhaeuser@posteo.de> wrote:
>>
>>> On 27. Jan 2023, at 10:29, Savva Mitrofanov <savvamtr@gmail.com> wrote:
>>>
>>> Missing comparison != 0 leads to broken logic condition.
>>
>> The actual issue appears to be FeaturesCompat vs FeaturesRoCompat (latter is hidden by your usage of the macro). Checking for != 0 is redundant (albeit required by the code style guideline for non-functional reasons). Please confirm and update the commit message if you agree.
>
> +1, the actual issue comes from using the wrong feature mask and not the != 0.
> If we get a v4, please update, else I can rewrite it myself.
>
> Reviewed-by: Pedro Falcato <pedro.falcato@gmail.com>
>
> --
> Pedro
next prev parent reply other threads:[~2023-01-30 8:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 9:29 [edk2-platforms][PATCH v3 00/11] Ext4Pkg: Code correctness and security improvements Savva Mitrofanov
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 01/11] Ext4Pkg: Fix memory leak in Ext4RetrieveDirent Savva Mitrofanov
2023-01-27 14:12 ` Pedro Falcato
2023-01-27 14:16 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 02/11] Ext4Pkg: Fix incorrect checksum metadata feature check Savva Mitrofanov
2023-01-27 10:02 ` Marvin Häuser
2023-01-27 14:29 ` Pedro Falcato
2023-01-30 8:38 ` Marvin Häuser [this message]
2023-01-30 8:42 ` Savva Mitrofanov
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 03/11] Ext4Pkg: Fix division by zero by adding check for s_inodes_per_group Savva Mitrofanov
2023-01-27 14:13 ` Pedro Falcato
2023-01-27 14:16 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 04/11] Ext4Pkg: Add inode number validity check Savva Mitrofanov
2023-01-27 14:19 ` Pedro Falcato
2023-02-02 10:15 ` Savva Mitrofanov
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 05/11] Ext4Pkg: Fix shift out of bounds in Ext4OpenSuperblock Savva Mitrofanov
2023-01-27 14:22 ` Pedro Falcato
2023-01-27 14:24 ` Marvin Häuser
2023-01-27 16:14 ` Savva Mitrofanov
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 06/11] Ext4Pkg: Corrects integer overflow check logic in DiskUtil Savva Mitrofanov
2023-01-27 14:24 ` Pedro Falcato
2023-01-27 16:10 ` Savva Mitrofanov
2023-01-27 16:21 ` Pedro Falcato
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 07/11] Ext4Pkg: Check that source file is directory in Ext4OpenInternal Savva Mitrofanov
2023-01-27 14:26 ` Pedro Falcato
2023-01-27 14:33 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 08/11] Ext4Pkg: Check VolumeName allocation correctness in Ext4GetVolumeName Savva Mitrofanov
2023-01-27 14:27 ` [edk2-devel] " Pedro Falcato
2023-01-27 14:34 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 09/11] Ext4Pkg: Add missing exit Status in Ext4OpenDirent Savva Mitrofanov
2023-01-27 14:28 ` Pedro Falcato
2023-01-27 14:34 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 10/11] Ext4Pkg: Fixes build on MSVC Savva Mitrofanov
2023-01-27 14:33 ` Pedro Falcato
2023-01-27 14:36 ` Marvin Häuser
2023-01-30 8:35 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 11/11] Ext4Pkg: Filter out directory entry names containing \0 as invalid Savva Mitrofanov
2023-01-27 10:04 ` Marvin Häuser
2023-01-27 14:09 ` Pedro Falcato
2023-01-27 14:14 ` Marvin Häuser
2023-01-30 8:48 ` Marvin Häuser
2023-01-30 8:19 ` Savva Mitrofanov
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=6BC46602-945D-4BB6-80AC-7E2D6ADA420A@posteo.de \
--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