From: Jan Kara <jack@suse.cz>
To: <linux-fsdevel@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>, Thomas Schmitt <scdbackup@gmx.net>,
Matthias Goergens <matthias.goergens@gmail.com>
Subject: [PATCH] isofs: Fix handling of directories with tight blocks
Date: Tue, 22 Sep 2026 14:19:13 +0200 [thread overview]
Message-ID: <20260922121912.2258134-2-jack@suse.cz> (raw)
Thomas has reported that after commit b2eb2e288604 ("isofs: Drop support
of directory entries straddling blocks") some isofs images of Fedora
miss some entries in some directories. The problem is triggered when
directory entries are packed in a block in such a way that they exactly
fit the block (which BTW mkisofs doesn't do so I didn't catch this bug
when testing with my images). Fix readdir and lookup code to properly
transition to the next block when directory block is tightly packed.
Link: https://bugzilla.redhat.com/show_bug.cgi?id=2535353
Reported-by: Thomas Schmitt <scdbackup@gmx.net>
Reported-by: Matthias Goergens <matthias.goergens@gmail.com>
Fixes: b2eb2e288604 ("isofs: Drop support of directory entries straddling blocks")
Signed-off-by: Jan Kara <jack@suse.cz>
---
fs/isofs/dir.c | 18 +++++++-----------
fs/isofs/namei.c | 14 ++++++++------
2 files changed, 15 insertions(+), 17 deletions(-)
I plan to push this fix to Linus at the end of the week.
diff --git a/fs/isofs/dir.c b/fs/isofs/dir.c
index c7ca7603e97a..5e541e765f54 100644
--- a/fs/isofs/dir.c
+++ b/fs/isofs/dir.c
@@ -110,25 +110,21 @@ static int do_isofs_readdir(struct inode *inode, struct file *file,
return 0;
}
- de = (struct iso_directory_record *) (bh->b_data + offset);
-
- de_len = *(unsigned char *)de;
-
+ de = (struct iso_directory_record *)(bh->b_data + offset);
/*
- * If the length byte is zero, we should move on to the next
- * CDROM sector. If we are at the end of the directory, we
- * kick out of the while loop.
+ * If we are at the end of a block (or at its zero-padded
+ * tail), move on to the next CDROM sector. If we are at the
+ * end of the directory, we'll abort the while loop.
*/
-
- if (de_len == 0) {
+ if (offset >= bufsize || de->length[0] == 0) {
brelse(bh);
bh = NULL;
- ctx->pos = (ctx->pos + ISOFS_BLOCK_SIZE) & ~(ISOFS_BLOCK_SIZE - 1);
+ ctx->pos = round_up(ctx->pos, bufsize);
block = ctx->pos >> bufbits;
offset = 0;
continue;
}
-
+ de_len = de->length[0];
block_saved = block;
offset_saved = offset;
offset += de_len;
diff --git a/fs/isofs/namei.c b/fs/isofs/namei.c
index 010682f5901a..e7efeea16451 100644
--- a/fs/isofs/namei.c
+++ b/fs/isofs/namei.c
@@ -74,18 +74,20 @@ isofs_find_entry(struct inode *dir, struct dentry *dentry,
return 0;
}
- de = (struct iso_directory_record *) (bh->b_data + offset);
-
- de_len = *(unsigned char *) de;
- if (!de_len) {
+ de = (struct iso_directory_record *)(bh->b_data + offset);
+ /*
+ * If we are at the end of the block or at its zero-padded
+ * length, move to the next block.
+ */
+ if (offset >= bufsize || de->length[0] == 0) {
brelse(bh);
bh = NULL;
- f_pos = (f_pos + ISOFS_BLOCK_SIZE) & ~(ISOFS_BLOCK_SIZE - 1);
+ f_pos = round_up(f_pos, bufsize);
block = f_pos >> bufbits;
offset = 0;
continue;
}
-
+ de_len = de->length[0];
block_saved = bh->b_blocknr;
offset_saved = offset;
offset += de_len;
--
2.51.0
next reply other threads:[~2026-09-22 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 12:19 Jan Kara [this message]
2026-09-22 14:59 ` [PATCH] isofs: Fix handling of directories with tight blocks Thomas Schmitt
2026-09-23 10:22 ` Jan Kara
2026-09-23 15:31 ` [PATCH] isofs: Always advance to the next block in readdir and lookup Matthias Goergens
2026-09-23 16:55 ` Jan Kara
2026-09-23 17:52 ` Matthias Goergens
2026-09-23 18:40 ` Jan Kara
2026-09-25 4:28 ` Matthias Goergens
2026-09-25 2:34 ` [syzbot ci] Re: isofs: Fix handling of directories with tight blocks syzbot ci
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=20260922121912.2258134-2-jack@suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthias.goergens@gmail.com \
--cc=scdbackup@gmx.net \
/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