All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Hungyu Lin <dennylin0707@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] inotify13: check rename cookie pairing after adjacent moves
Date: Fri, 30 Oct 2026 00:31:28 +0000	[thread overview]
Message-ID: <20261030003128.3782-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20261029210701.80050-1-dennylin0707@gmail.com>

Hi Hungyu,

On Thu Oct 29, 2026, Hungyu Lin <dennylin0707@gmail.com> wrote:
> inotify13: check rename cookie pairing after adjacent moves

> +/*\
> + * Verify that two IN_MOVED_FROM events that differ only in their rename
> + * cookie are not coalesced.
> + *
> + * inotify(7) allows coalescing only of events with identical wd, mask,

Use :manpage:`inotify(7)` in the RST doc comment so that the test catalog
renders a link to the man page.

> +static void cleanup(void)
> +{
> +	if (fd_notify >= 0)
> +		SAFE_CLOSE(fd_notify);
> +}

Use "if (fd_notify != -1)" to check file descriptor validity in cleanup(),
matching the -1 initialization convention.

> +static struct tst_test test = {
> +	.test = verify_inotify,
> +	.tcnt = ARRAY_SIZE(tcases),
> +	.setup = setup,
> +	.cleanup = cleanup,
> +	.needs_tmpdir = 1,
> +};

Since this is a kernel regression test, add .tags with the "linux-git" fix
commit hash in struct tst_test once the kernel fix is merged.

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-10-30  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 21:07 [PATCH v4] inotify13: check rename cookie pairing after adjacent moves Hungyu Lin
2026-10-29 21:07 ` [LTP] " Hungyu Lin
2026-10-30  0:31 ` linuxtestproject.agent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-29 17:49 [PATCH v3] " Hungyu Lin
2026-10-29 19:58 ` [LTP] " linuxtestproject.agent
2026-10-28  5:15 [PATCH v2] " Hungyu Lin
2026-10-29 19:56 ` [LTP] " linuxtestproject.agent
2026-10-27 19:19 [PATCH] " Hungyu Lin
2026-10-29 19:57 ` [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=20261030003128.3782-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=dennylin0707@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.