From: linuxtestproject.agent@gmail.com
To: Runli <mingyu.he@shopee.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] pty09: Cap RLIMIT_NOFILE-based slave PTY opens
Date: Tue, 14 Jul 2026 08:06:28 +0000 [thread overview]
Message-ID: <20260714080628.4032-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260714031545.64932-1-mingyu.he@shopee.com>
Hi Runli,
On Tue, 14 Jul 2026, Runli wrote:
> pty09: Cap RLIMIT_NOFILE-based slave PTY opens
> + if (max_pid_num > MAX_SLAVE_OPENS) {
> + max_pid_num = MAX_SLAVE_OPENS;
> + tst_res(TINFO, "Number of pids is too large, capped at: %u",
> + max_pid_num);
> + }
The value being capped is derived from RLIMIT_NOFILE (open file descriptor
slots), not process IDs. "Number of pids is too large" describes the wrong
resource.
The commit message itself uses the accurate term ("slave opens"). Suggest
aligning the TINFO message with that:
tst_res(TINFO, "Number of slave opens is too large, capped at: %u",
max_pid_num);
Pre-existing issue: the containing function count_avail_pid() and its local
variable max_pid_num carry the same "pid" misnomer for what is really an
open-fd-slot count. Not introduced by this patch, but worth noting.
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
next prev parent reply other threads:[~2026-07-14 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 3:15 [LTP] [PATCH v2] pty09: Cap RLIMIT_NOFILE-based slave PTY opens Runli via ltp
2026-07-14 8:06 ` linuxtestproject.agent [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-09 7:49 [LTP] [PATCH] " Runli via ltp
2026-07-09 10:33 ` [LTP] " linuxtestproject.agent
2026-07-10 13:48 ` Cyril Hrubis
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=20260714080628.4032-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=mingyu.he@shopee.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