From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Cc: lidong.chen@oracle.com, fengtao40@huawei.com, yanan@huawei.com,
daniel.kiper@oracle.com, lichenca2005@gmail.com
Subject: Re: [PATCH v2 0/5] fs/iso9660: Fix out-of-bounds read
Date: Fri, 20 Jan 2023 12:49:40 +0100 [thread overview]
Message-ID: <25717393172200334337@scdbackup.webframe.org> (raw)
In-Reply-To: <EF18BFAA-2C70-47D4-9FBB-B8E093E0AA21@ORACLE.COM>
Hi,
Lidong Chen wrote:
> I ran grub-fastest with both ce_loop ISO files. The endless loops were
> detected and Grub exited accordingly.
Good.
> I didn't know where the grub error message
> were stored in case of grub-fastest.
So you don't see an error message ?
I had the same problem a while ago, when i tried to check that my thoughts
about the loop end condition in grub_iso9660_susp_iterate() are correct.
(This is now covered by your patch 2.)
> But, I traced with gdb, and saw the code reported the error.
It's on my todo list to learn how to prepare grub-fstest for working with
gdb. Currently gdb says "No debugging symbols found in ./grub-fstest".
> If the diff looks good, I will send the v3 patches set.
I have no objections.
If patches 1 to 4 are included in v3, please tell whether they have changed
towards v2. (I see no reason why they should change. But if they do, i'll
have to compare them with the earlier versions.)
---------------------------------------------------------------------
I still riddle about how the error message can become visible to the user.
I don't get ideas for that from
https://www.gnu.org/software/grub/manual/grub-dev/grub-dev.html#Error-Handling
I wonder what is supposed to happen to the "textual message" component of
a grub_error() call. Under which conditions will it be displayed ?
And where ?
Have a nice day :)
Thomas
next prev parent reply other threads:[~2023-01-20 11:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 8:23 [PATCH v2 0/5] fs/iso9660: Fix out-of-bounds read Lidong Chen
2023-01-18 8:23 ` [PATCH v2 1/5] fs/iso9660: Add check to prevent infinite loop Lidong Chen
2023-01-18 16:07 ` Thomas Schmitt
2023-01-19 1:34 ` Lidong Chen
2023-01-18 8:23 ` [PATCH v2 2/5] fs/iso9660: Prevent read past the end of system use area Lidong Chen
2023-01-18 16:12 ` Thomas Schmitt
2023-01-18 8:23 ` [PATCH v2 3/5] fs/iso9660: Avoid reading past the entry boundary Lidong Chen
2023-01-18 16:14 ` Thomas Schmitt
2023-01-18 8:23 ` [PATCH v2 4/5] fs/iso9660: Incorrect check for " Lidong Chen
2023-01-18 16:17 ` Thomas Schmitt
2023-01-18 8:23 ` [PATCH v2 5/5] fs/iso9660: Prevent skipping CE or ST at start of continuation area Lidong Chen
2023-01-18 16:21 ` Thomas Schmitt
2023-01-19 1:25 ` Lidong Chen
2023-01-18 16:31 ` [PATCH v2 0/5] fs/iso9660: Fix out-of-bounds read Thomas Schmitt
2023-01-19 1:22 ` Lidong Chen
2023-01-19 11:58 ` Thomas Schmitt
2023-01-20 2:29 ` Lidong Chen
2023-01-20 11:49 ` Thomas Schmitt [this message]
2023-01-20 19:31 ` Lidong Chen
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=25717393172200334337@scdbackup.webframe.org \
--to=scdbackup@gmx.net \
--cc=daniel.kiper@oracle.com \
--cc=fengtao40@huawei.com \
--cc=grub-devel@gnu.org \
--cc=lichenca2005@gmail.com \
--cc=lidong.chen@oracle.com \
--cc=yanan@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.