Linux filesystem development
 help / color / mirror / Atom feed
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: Thu, 24 Sep 2026 23:13:55 +0800	[thread overview]
Message-ID: <20260924151356.3287733-1-matthias.goergens@gmail.com> (raw)
In-Reply-To: <w3rnunloyshklgq4ocr4jsullzhaey6u7odstfoyhd4usbfppo@m33jyem5jgrf>

Hi Honza,

On Thu 24-09-26 17:03:50, Jan Kara wrote:
> Based on the standard empty directory blocks are not allowed (there must be
> at least one directory record in each directory block). So I'd perhaps just
> add checks to refuse them. Then the limit on the number of sections of inode
> description already present in isofs_read_level3_size() will naturally take
> care of the rest.

That's simpler, thanks.

Hui, would you like to do that?  If not, I'll send it in a few days.
Either way, I'll first check a set of real images for empty directory
blocks, so we know the check doesn't reject discs that mount today.

Thanks,
Matthias

  reply	other threads:[~2026-09-24 15:14 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 [this message]
2026-09-25  4:38       ` Matthias Goergens
2026-09-25  9:28         ` Jan Kara
2026-09-25 11:22           ` Matthias Goergens
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=20260924151356.3287733-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