From: Matthias Goergens <matthias.goergens@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] kdev_t: shift in dev_t in MKDEV()
Date: Mon, 28 Sep 2026 06:49:58 +0800 [thread overview]
Message-ID: <20260927224958.508964-1-matthias.goergens@gmail.com> (raw)
MKDEV(ma, mi) evaluates ((ma) << MINORBITS) in whatever type the
caller passes, usually int. For majors >= 2048 (legal: majors go up
to 4095) the result exceeds INT_MAX, which C11 leaves undefined for
a signed left shift; shifting a negative ma is undefined regardless
of the major's value. In practice, on the compilers and two's
complement targets the kernel supports, both cases wrap to the
intended bit pattern; this patch makes the macro well defined
regardless by casting the major to dev_t before shifting. For major and
minor numbers in range, the device number it produces is unchanged.
isofs feeds the Rock Ridge 'PN' entry's dev_high and dev_low into
MKDEV() while holding them in int variables (fs/isofs/rock.c), so a
crafted image can drive this exact shift. Fixing the macro covers
every caller instead of just that one.
Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
---
include/linux/kdev_t.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/kdev_t.h b/include/linux/kdev_t.h
index 4856706fbfeb..2dbbd47f1e68 100644
--- a/include/linux/kdev_t.h
+++ b/include/linux/kdev_t.h
@@ -9,7 +9,7 @@
#define MAJOR(dev) ((unsigned int) ((dev) >> MINORBITS))
#define MINOR(dev) ((unsigned int) ((dev) & MINORMASK))
-#define MKDEV(ma,mi) (((ma) << MINORBITS) | (mi))
+#define MKDEV(ma, mi) (((dev_t)(ma) << MINORBITS) | (mi))
#define print_dev_t(buffer, dev) \
sprintf((buffer), "%u:%u\n", MAJOR(dev), MINOR(dev))
--
2.55.0
next reply other threads:[~2026-09-27 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 22:49 Matthias Goergens [this message]
2026-09-28 1:21 ` Andrew Morton
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=20260927224958.508964-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=akpm@linux-foundation.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®