diff options
| author | Matthias Goergens <matthias.goergens@gmail.com> | 2026-09-28 06:49:58 +0800 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2026-10-08 23:06:51 -0700 |
| commit | 90cf0c5be5c82e5138713f8fd3a737855725adc3 (patch) | |
| tree | a0bb7119a027f5a7ce6a4c6131777c403d226def /tools/lib/python/kdoc/python_version.py | |
| parent | 443614b796aa7dddafa6492efbbf7b17612e152d (diff) | |
| download | linux-next-90cf0c5be5c82e5138713f8fd3a737855725adc3.tar.gz linux-next-90cf0c5be5c82e5138713f8fd3a737855725adc3.zip | |
kdev_t: shift in dev_t in MKDEV()
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.
Link: https://lore.kernel.org/20260927224958.508964-1-matthias.goergens@gmail.com
Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Jan Kara <jack@suse.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
