public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: acervesato@ltp-agent
To: Ricardo Branco <rbranco@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] userfaultfd: Use two-step handshake to probe features
Date: Sat, 11 Apr 2026 09:46:23 +0000	[thread overview]
Message-ID: <20260411094623.3963-1-ltp-ci@noreply.github.com> (raw)
In-Reply-To: <20260411092452.211540-1-rbranco@suse.de>

Hi Ricardo,

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.

On Sat, 11 Apr 2026 11:24:51 +0200, Ricardo Branco wrote:
> userfaultfd: Use two-step handshake to probe features

> +       if (!(uffdio_api.features & UFFD_FEATURE_PAGEFAULT_FLAG_WP))
> +               tst_brk(TCONF, "UFFD_FEATURE_PAGEFAULT_FLAG_WP not supported");
> +       SAFE_CLOSE(uffd);

tst_brk() longjmps out of run(), so SAFE_CLOSE never executes — close uffd
before calling tst_brk(). userfaultfd05.c also has no .cleanup, so the page
mmap from set_pages() leaks too; add .cleanup = reset_pages to struct tst_test.

[...]

> +       if (!(uffdio_api.features & UFFD_FEATURE_POISON))
> +               tst_brk(TCONF, "UFFD_FEATURE_POISON not supported");
> +       SAFE_CLOSE(uffd);

Same issue: close uffd before calling tst_brk().

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-04-11 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11  9:24 [LTP] [PATCH] userfaultfd: Use two-step handshake to probe features Ricardo Branco
2026-04-11  9:46 ` acervesato [this message]
2026-04-11 10:39 ` [LTP] " acervesato

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=20260411094623.3963-1-ltp-ci@noreply.github.com \
    --to=acervesato@ltp-agent \
    --cc=ltp@lists.linux.it \
    --cc=rbranco@suse.de \
    /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