Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Avinesh Kumar <avinesh.kumar@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] syscalls: rename11: Convert test to new API
Date: Thu, 13 Aug 2026 20:44:27 +0000	[thread overview]
Message-ID: <20260813204427.8855-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260813192649.192136-1-avinesh.kumar@suse.com>

Hi Avinesh,

On Thu, Aug 13, 2026, Avinesh Kumar wrote:
> syscalls: rename11: Convert test to new API

> syscalls: rename11: Convert test to new API
>
> Signed-off-by: Avinesh Kumar <avinesh.kumar@suse.com>

Could the commit message include a sentence explaining why this conversion is
needed? This changes lifecycle, device handling, result reporting, and cleanup
semantics, so it is not a trivial change for which the subject alone explains
the motivation.

> +/*\
> + * Verify that :manpage:`rename(2)` fails with:
> + *
> + * - ``ELOOP`` when too many symbolic links are encountered while resolving
> + *   oldpath or newpath.
> + * - ``EROFS`` when the file is on a read-only file system.
> + * - ``EMLINK`` when oldpath is a directory and the link count of the parent
> + *   directory of newpath would exceed ``LINK_MAX``.
> + */

Could the description state that root is required to mount and remount the
test filesystem for the EROFS case? Tests setting ``.needs_root`` must
document why those privileges are needed.

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-13 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 19:26 [LTP] [PATCH] syscalls: rename11: Convert test to new API Avinesh Kumar via ltp
2026-08-13 20:44 ` 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=20260813204427.8855-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=avinesh.kumar@suse.com \
    --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