From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] shmctl03: Fix shmall clamped to UINT32_MAX in 32bit compat mode
Date: Tue, 10 Nov 2026 10:58:18 +0100 [thread overview]
Message-ID: <avLquujJd9vV8MFS@yuki.lan> (raw)
In-Reply-To: <20261026151638.578859-1-pvorel@suse.cz>
Hi!
> Unlike shmmax, the kernel's compat shmctl(IPC_INFO) path does not clamp
> shmall but truncates the 64-bit value into the 32-bit compat shminfo
> (see copy_compat_shminfo_to_user() in ipc/shm.c, originally changed by
> af7c693f14606 ("Cap shmmax at INT_MAX in compat shminfo") in kernel
> v2.6.22.
Sigh, this does look very random, one value is truncated and one is
saturated. I wonder if we should send a patch to kernel so that both
values are saturated, that would make much more sense to me.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-11-10 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 15:16 [LTP] [PATCH 1/1] shmctl03: Fix shmall clamped to UINT32_MAX in 32bit compat mode Petr Vorel
2026-10-26 16:35 ` [LTP] " linuxtestproject.agent
2026-11-10 9:58 ` Cyril Hrubis [this message]
2026-11-10 11:13 ` [LTP] [PATCH 1/1] " Petr Vorel
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=avLquujJd9vV8MFS@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.