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] landlock04: Fix false TFAIL in _test_truncate() deny path
Date: Mon, 24 Aug 2026 10:38:32 +0000	[thread overview]
Message-ID: <20260824103832.4058-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260824101525.176017-1-avinesh.kumar@suse.com>

Hi Avinesh,

On Mon, Aug 24, 2026, Avinesh Kumar wrote:
> landlock04: Fix false TFAIL in _test_truncate() deny path

> +	fd = exp_err ? open(FILE_TRUNCATE, O_WRONLY, PERM_MODE)
> +		     : SAFE_OPEN(FILE_TRUNCATE, O_WRONLY, PERM_MODE);
>  	if (fd != -1) {

Could the deny branch report open() errors other than EACCES? EACCES is an
expected reason to skip ftruncate() when write access is denied, but open(2)
can also fail with EMFILE, ENFILE, or ENOMEM. Those failures currently take
the same fd == -1 path, silently skip the ftruncate() assertion, and let the
variant pass without testing it.

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-24 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 10:15 [LTP] [PATCH] landlock04: Fix false TFAIL in _test_truncate() deny path Avinesh Kumar via ltp
2026-08-24 10:38 ` linuxtestproject.agent [this message]
2026-08-24 13:57   ` [LTP] [PATCH v2] " Avinesh Kumar via ltp
2026-08-24 14:04     ` Andrea Cervesato via ltp
2026-08-24 14:42     ` [LTP] " linuxtestproject.agent
2026-08-25  4:38     ` [LTP] [PATCH v2] " Petr Vorel

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=20260824103832.4058-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