From: Matthias Goergens <matthias.goergens@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] isofs: tie the name conversion buffer to its bound
Date: Tue, 22 Sep 2026 23:55:22 +0800 [thread overview]
Message-ID: <20260922155524.1993425-1-matthias.goergens@gmail.com> (raw)
Two cleanups around the scratch buffer isofs_readdir() and
isofs_lookup() hand to the name converters. No functional change; the
first patch's assertions hold on the current code.
Found while looking at something else: get_joliet_filename() has been
passing PAGE_SIZE as its output bound since b2eb2e288604 shrank the
buffer to 1024, which is safe only because de->name_len is a single
byte. That seemed worth writing down in a form the compiler checks.
Matthias Goergens (2):
isofs: size the name conversion buffer from a named constant
isofs: bound the Joliet iocharset conversion by the output buffer
fs/isofs/dir.c | 9 ++++++++-
fs/isofs/isofs.h | 9 +++++++++
fs/isofs/joliet.c | 25 ++++++++++++++++++++-----
fs/isofs/namei.c | 2 +-
fs/isofs/rock.c | 3 +++
5 files changed, 41 insertions(+), 7 deletions(-)
base-commit: 40288c9206c17eb66a603262e06a58d300d0f279
--
2.55.0
next reply other threads:[~2026-09-22 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 15:55 Matthias Goergens [this message]
2026-09-22 15:55 ` [PATCH 1/2] isofs: size the name conversion buffer from a named constant Matthias Goergens
2026-09-24 12:35 ` Jan Kara
2026-09-22 15:55 ` [PATCH 2/2] isofs: bound the Joliet iocharset conversion by the output buffer Matthias Goergens
2026-09-24 12:40 ` Jan Kara
2026-09-24 10:02 ` [PATCH 0/2] isofs: tie the name conversion buffer to its bound 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=20260922155524.1993425-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®