From: linuxtestproject.agent@gmail.com
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] aio_cancel: Fix incorrect strerror() usage
Date: Tue, 28 Apr 2026 14:44:17 +0000 [thread overview]
Message-ID: <20260428144417.4093-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260428133233.28050-1-mdoucha@suse.cz>
Hi Martin,
--- [PATCH 1/2] ---
On 2026-04-28, Martin Doucha wrote:
> aio_cancel: Fix incorrect strerror() usage
This is fixing a real bug but both patches in this series are missing
Fixes: tags.
--- [PATCH 2/2] ---
On 2026-04-28, Martin Doucha wrote:
> aio_cancel_6-1: Rewrite test
> + if (gret != AIO_CANCELED) {
> + printf(TNAME " Unexpected aio_cancel() return value: %s\n",
> + strerror(gret));
strerror() expects an errno value; AIO_CANCELED, AIO_NOTCANCELED, and
AIO_ALLDONE are not errno values (they are 0, 1, 2 on Linux, mapping to
"Success", "Operation not permitted", "No such file or directory").
Use "%d" to print the raw integer instead.
Pre-existing issues noticed in the surrounding code (not introduced
by this patch):
- 5-1.c:70, 7-1.c:56 — nanosleep() used for synchronization in a
polling loop (sleep-based sync).
---
Note:
Our agent completed the review of the patch. 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-28 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 13:32 [LTP] [PATCH 1/2] aio_cancel: Fix incorrect strerror() usage Martin Doucha
2026-04-28 14:44 ` linuxtestproject.agent [this message]
2026-04-29 7:13 ` Andrea Cervesato via ltp
-- strict thread matches above, loose matches on Subject: below --
2026-04-29 14:53 [LTP] [PATCH v2 " Martin Doucha
2026-04-29 15:20 ` [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=20260428144417.4093-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=mdoucha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox