From: linuxtestproject.agent@gmail.com
To: Michael Menasherov <mmenashe@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] futex_wake05: Add EFAULT error coverage test
Date: Thu, 16 Jul 2026 15:15:17 +0000 [thread overview]
Message-ID: <20260716151517.4088-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260716133108.13003-2-mmenashe@redhat.com>
Hi Michael,
On Thu, 16 Jul 2026 16:31:07 +0300, Michael Menasherov <mmenashe@redhat.com> wrote:
> futex_wake05: Add EFAULT error coverage test
--- [PATCH 1/2] ---
> +/*\
> + * Check that futex(FUTEX_WAKE) returns EFAULT when uaddr points to
The doc block is rendered in the test catalog as reStructuredText. When
referring to a raw syscall in a /*\ ... */ block, the :manpage: role is
required (c-tests.md rule 19). Should this read:
Check that :manpage:`futex(2)` with ``FUTEX_WAKE`` returns EFAULT
when uaddr points to ...
--- [PATCH 2/2] ---
> +/*\
> + * Check that futex(FUTEX_CMP_REQUEUE) returns EFAULT when uaddr or
Same :manpage: issue: "futex(FUTEX_CMP_REQUEUE)" should be
":manpage:`futex(2)`" with "``FUTEX_CMP_REQUEUE``" for the operation.
> +/futex_cmp_requeue03
The git.md rule requires .gitignore entries to be kept sorted. The
existing file already has /futex_cmp_requeue01 and /futex_cmp_requeue02
near the top. Appending /futex_cmp_requeue03 at the end leaves it out
of order; it belongs immediately after /futex_cmp_requeue02.
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-16 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 13:31 [LTP] [PATCH v17 0/2] futex: Add EFAULT error coverage tests Michael Menasherov via ltp
2026-07-16 13:31 ` [LTP] [PATCH v17 1/2] futex_wake05: Add EFAULT error coverage test Michael Menasherov via ltp
2026-07-16 15:15 ` linuxtestproject.agent [this message]
2026-07-17 10:01 ` [LTP] " Cyril Hrubis
2026-07-16 13:31 ` [LTP] [PATCH v17 2/2] futex_cmp_requeue03: " Michael Menasherov via ltp
-- strict thread matches above, loose matches on Subject: below --
2026-06-21 15:09 [LTP] [PATCH v16 1/2] futex_wake05: " Michael Menasherov via ltp
2026-06-22 9:44 ` [LTP] " linuxtestproject.agent
2026-06-16 18:30 [LTP] [PATCH v15 1/2] " Michael Menasherov via ltp
2026-06-16 19:47 ` [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=20260716151517.4088-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=mmenashe@redhat.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