Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] shmctl03: Fix 32-bit compat mode failure by adjusting comparisons for compat mode truncation
Date: Wed, 19 Aug 2026 09:39:59 +0000	[thread overview]
Message-ID: <20260819093959.9153-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260819083907.26866-1-wegao@suse.com>

Hi Wei,

On Aug 19, 2026, Wei Gao wrote:
> shmctl03: Fix 32-bit compat mode failure by adjusting comparisons for compat mode truncation

> +#define TST_ASSERT_SATURATED_INT   0x01
> +#define TST_ASSERT_BITWISE         0x02
> +
>  /*
>   * Same as tst_assert_int() but for unsigned long.
>   */
>  void tst_assert_ulong(const char *file, const int lineno,
> +                      const char *path, unsigned long val, int flags);

Could these new public flags and the flags parameter be documented with
kernel-doc? The existing comment does not explain that one mode clamps at
INT_MAX while the other keeps the low 32 bits. [Low]

> +		/*
> +		 * On 64-bit kernel, shmmax is clamped to INT_MAX for 32-bit
> +		 * compat syscall, while shmmni and shmall are truncated
> +		 * to 32-bit.
> +		 */
> +		TST_ASSERT_ULONG(PATH_KERN_SHMMNI, info.shmmni, TST_ASSERT_BITWISE);

Could shmmni keep the direct comparison, and could the comment omit it?
In Linux 7.2, ipc_namespace.shm_ctlmni is an int, the sysctl limits it to
0..ipc_mni, and the compat path copies it directly to compat_ulong_t, so no
truncation occurs. [Low]

Verdict - Needs revision

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2026-08-19  9:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07  9:26 [LTP] [PATCH v1] shmctl03: Fix 32-bit compat mode failure by forcing limits Wei Gao via ltp
2026-04-10 13:14 ` Andrea Cervesato via ltp
2026-04-10 14:12   ` Wei Gao via ltp
2026-04-10 14:32     ` Andrea Cervesato via ltp
2026-04-13  6:19 ` [LTP] [PATCH v2] shmctl03: Fix 32-bit compat mode failure by adjusting comparisons for compat mode truncation Wei Gao via ltp
2026-04-29  8:04   ` [LTP] " linuxtestproject.agent
2026-04-29 11:18   ` [LTP] [PATCH v3] " Wei Gao via ltp
2026-04-29 12:33     ` [LTP] " linuxtestproject.agent
2026-04-30  3:47     ` [LTP] [PATCH v4] " Wei Gao via ltp
2026-04-30  6:35       ` [LTP] " linuxtestproject.agent
2026-05-06 17:28         ` Andrea Cervesato via ltp
2026-05-07  9:51           ` Wei Gao via ltp
2026-05-07 10:01             ` Andrea Cervesato via ltp
2026-08-19  3:17       ` [LTP] [PATCH v5] " Wei Gao via ltp
2026-08-19  3:48         ` [LTP] " linuxtestproject.agent
2026-08-19  7:11           ` Andrea Cervesato via ltp
2026-08-19  8:38         ` [LTP] [PATCH v6] " Wei Gao via ltp
2026-08-19  9:39           ` linuxtestproject.agent [this message]

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=20260819093959.9153-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    --cc=wegao@suse.com \
    /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