From: Andrew Hamilton <adhamilt@gmail.com>
To: grub-devel@gnu.org
Cc: daniel.kiper@oracle.com
Subject: Re: [PATCH 0/1] One More NTFS Fuzzing Fix
Date: Sat, 26 Jul 2025 07:58:31 -0500 [thread overview]
Message-ID: <CA+04=DYQa7BK9HUcrAc6__NO_M3+G4PsHvionex93EmETVpnqw@mail.gmail.com> (raw)
In-Reply-To: <20250601155222.21934-1-adhamilt@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 853 bytes --]
Hello,
Just re-raising this for consideration.
Thank you,
Andrew
On Sun, Jun 1, 2025 at 10:52 AM Andrew Hamilton <adhamilt@gmail.com> wrote:
> I took one last pass at my attempts at ad-hoc fuzzing of NTFS
> with the goal of improving coverage and letting the fuzzer run
> for a while. After rebuilding afl++ to allow larger file inputs
> that are more representative of real NTFS file systems, it was
> uncovered that my last fix to address NTFS test regressions
> left a possible access violation in find_attr.
>
> This fixes the last remaining fuzzing issue uncovered.
>
> Confirmed that NTFS test cases still pass.
>
> Andrew Hamilton (1):
> fs/ntfs.c: Correct possible access violation on next_attribute
>
> grub-core/fs/ntfs.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> --
> 2.39.5
>
>
[-- Attachment #1.2: Type: text/html, Size: 1249 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
prev parent reply other threads:[~2025-07-26 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 15:52 [PATCH 0/1] One More NTFS Fuzzing Fix Andrew Hamilton
2025-06-01 15:52 ` [PATCH 1/1] fs/ntfs.c: Correct next_attribute validation Andrew Hamilton
2025-10-24 16:21 ` Daniel Kiper
2025-07-26 12:58 ` Andrew Hamilton [this message]
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='CA+04=DYQa7BK9HUcrAc6__NO_M3+G4PsHvionex93EmETVpnqw@mail.gmail.com' \
--to=adhamilt@gmail.com \
--cc=daniel.kiper@oracle.com \
--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 NNTP newsgroup(s).