From: linuxtestproject.agent@gmail.com
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] syscalls: Add epoll_create03
Date: Thu, 23 Apr 2026 11:17:55 +0000 [thread overview]
Message-ID: <20260423111755.4154-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260423095834.11932-2-chrubis@suse.cz>
Hi Cyril,
--- [PATCH 3/8] ---
On 2026-04-23, Cyril Hrubis wrote:
> syscalls: Add epoll_wait09
> -epoll_wait08 epoll_wait08
> +epoll_wait09 epoll_wait09
This replaces the epoll_wait08 entry instead of adding epoll_wait09
alongside it. epoll_wait08 will be built but never run.
> That checks that events from recursive epoll are propagated correctly.
"That checks..." is a dangling clause; the body must stand alone as a
sentence (e.g. "Test that checks...").
--- [PATCH 5/8] ---
On 2026-04-23, Cyril Hrubis wrote:
> syscall: Add epoll_wait10
Prefix typo: "syscall:" should be "syscalls:" (all other patches in
this series use "syscalls:").
--- [PATCH 6/8] ---
On 2026-04-23, Cyril Hrubis wrote:
> syscalls: Add epoll_wait11
>
> A test that chcecks that EPOLLHUP is generated properly [...]
Typo: "chcecks" -> "checks".
> + TST_PROCESS_STATE_WAIT(pid, 'S', 0);
> + SAFE_CLOSE(fds[1]);
> + SAFE_CLOSE(fds[0]);
> + SAFE_CLOSE(efd);
> +}
> +
> +static void cleanup(void)
> +{
> + if (fds[1] > 0)
> + SAFE_CLOSE(fds[1]);
fds[] and efd are closed in run() but not reset to -1; cleanup() then
double-closes them on every run (TBROK). Reset each to -1 after
SAFE_CLOSE in run(), and use != -1 guards in cleanup() per LTP
convention.
--- [PATCH 7/8] ---
On 2026-04-23, Cyril Hrubis wrote:
> + TST_PROCESS_STATE_WAIT(pid, 'S', 0);
> + SAFE_CLOSE(fds[0]);
> + SAFE_CLOSE(fds[1]);
> + SAFE_CLOSE(efd);
> +}
> +
> +static void cleanup(void)
> +{
> + if (fds[1] > 0)
> + SAFE_CLOSE(fds[1]);
Same double-close defect as epoll_wait11; apply the same fix.
---
Note:
Our agent completed the review of the patch. The full review can be
found at: https://github.com/linux-test-project/ltp-agent/actions/runs/24831850683
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-04-23 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 9:58 [LTP] [PATCH 0/8] Add more epoll tests Cyril Hrubis
2026-04-23 9:58 ` [LTP] [PATCH 1/8] syscalls: Add epoll_create03 Cyril Hrubis
2026-04-23 11:17 ` linuxtestproject.agent [this message]
2026-04-23 11:47 ` [LTP] " Cyril Hrubis
2026-04-23 9:58 ` [LTP] [PATCH 2/8] syscalls: Add epoll_wait08 Cyril Hrubis
2026-04-23 9:58 ` [LTP] [PATCH 3/8] syscalls: Add epoll_wait09 Cyril Hrubis
2026-04-23 9:58 ` [LTP] [PATCH 4/8] syscalls: Add epoll_ctl06 Cyril Hrubis
2026-04-23 9:58 ` [LTP] [PATCH 5/8] syscall: Add epoll_wait10 Cyril Hrubis
2026-04-23 9:58 ` [LTP] [PATCH 6/8] syscalls: Add epoll_wait11 Cyril Hrubis
2026-04-23 9:58 ` [LTP] [PATCH 7/8] syscalls: Add epoll_wait12 Cyril Hrubis
2026-04-23 9:58 ` [LTP] [PATCH 8/8] syscalls: Remove old epoll-ltp test Cyril Hrubis
-- strict thread matches above, loose matches on Subject: below --
2026-04-23 12:03 [LTP] [PATCH v2 1/8] syscalls: Add epoll_create03 Cyril Hrubis
2026-04-23 13:43 ` [LTP] " linuxtestproject.agent
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=20260423111755.4154-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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