From: Matthias Goergens <matthias.goergens@gmail.com>
To: jack@suse.cz
Cc: benquike@gmail.com, brauner@kernel.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] isofs: reject short directory records in isofs_read_level3_size()
Date: Fri, 25 Sep 2026 19:22:09 +0800 [thread overview]
Message-ID: <20260925112209.911126-1-matthias.goergens@gmail.com> (raw)
In-Reply-To: <cmlro2xzle2aa7ebflvxhbcv74mea7p6qvxhin6egpdvyzyuxh@s45tpgxdal3n>
Hi Honza,
On Fri 25-09-26 11:28:18, Jan Kara wrote:
> OK, thanks for checking! BTW how did you do the check. Have you've downloaded
> all the images?
Gotta use that 10 Gbps fibre-to-the-home broadband for something! But
no, I used a script: archive.org serves range requests, so it fetched
only the volume descriptors, path tables and directory extents of each
image, about half a megabyte per disc, and parsed those. I'm happy to
share the script and the list of images.
> So yes, just keep the code skipping empty blocks and I'd just limit
> the number of sections + empty blocks to 100.
Will do, unless Hui would like to take it.
Thanks,
Matthias
next prev parent reply other threads:[~2026-09-25 11:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 22:25 [PATCH] isofs: reject short directory records in isofs_read_level3_size() Hui Peng
2026-09-23 17:52 ` Matthias Goergens
2026-09-24 15:03 ` Jan Kara
2026-09-24 15:13 ` Matthias Goergens
2026-09-25 4:38 ` Matthias Goergens
2026-09-25 9:28 ` Jan Kara
2026-09-25 11:22 ` Matthias Goergens [this message]
2026-09-26 8:35 ` [PATCH] isofs: bound empty directory blocks " Matthias Goergens
2026-09-29 10:57 ` Jan Kara
2026-09-30 3:39 ` Matthias Goergens
2026-09-30 10:33 ` Jan Kara
2026-10-01 10:30 ` Matthias Goergens
2026-10-02 10:55 ` Jan Kara
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=20260925112209.911126-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=benquike@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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