All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lapi/prctl: add more fallback definitions
Date: Mon,  3 Aug 2026 14:38:24 +0000	[thread overview]
Message-ID: <20260803143824.9095-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260803-cve-ghostlock-v3-1-cde83fa429b7@suse.com>

Hi Andrea,

On Mon, 3 Aug 2026, Andrea Cervesato wrote:
> lapi/prctl: add more fallback definitions

--- [PATCH 1/2] ---

> +#ifndef PR_SET_MM_MAP
> +# define PR_SET_MM_MAP	14
> +#endif
> +#ifndef PR_SET_MM_MAP_SIZE
> +# define PR_SET_MM_MAP_SIZE	15
> +#endif
> +
> +#if !(HAVE_STRUCT_PRCTL_MM_MAP) && !defined(PR_SET_MM_MAP)

Could this struct guard depend only on HAVE_STRUCT_PRCTL_MM_MAP?

PR_SET_MM_MAP is defined immediately above, so !defined(PR_SET_MM_MAP) is
always false here. Systems missing struct prctl_mm_map therefore skip the
fallback even when HAVE_STRUCT_PRCTL_MM_MAP is false, and the second patch
cannot compile there.

--- [PATCH 2/2] ---

> +	SAFE_PRCTL(PR_SET_MM, PR_SET_MM_MAP_SIZE, (unsigned long)&sz, 0, 0);

Could this test set .min_kver = "3.18", or report TCONF when this operation
is unavailable?

PR_SET_MM_MAP_SIZE was added in Linux 3.18, while
CONFIG_CHECKPOINT_RESTORE predates it. A 3.5 through 3.17 kernel with that
configuration reaches setup(), rejects this operation, and SAFE_PRCTL()
reports TBROK for an unsupported reproducer feature.

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-03 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 12:26 [LTP] [PATCH v3 0/2] Reproducer for ghostlock Andrea Cervesato
2026-08-03 12:26 ` [LTP] [PATCH v3 1/2] lapi/prctl: add more fallback definitions Andrea Cervesato
2026-08-03 14:38   ` linuxtestproject.agent [this message]
2026-08-04  7:39     ` [LTP] " Andrea Cervesato via ltp
2026-08-03 12:26 ` [LTP] [PATCH v3 2/2] cve: add CVE-2026-43499 reproducer Andrea Cervesato
  -- strict thread matches above, loose matches on Subject: below --
2026-08-03  8:10 [LTP] [PATCH v2 1/2] lapi/prctl: add more fallback definitions Andrea Cervesato
2026-08-03  9:36 ` [LTP] " linuxtestproject.agent
2026-08-01 10:34 [LTP] [PATCH 1/2] " Andrea Cervesato
2026-08-01 11:27 ` [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=20260803143824.9095-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=andrea.cervesato@suse.de \
    --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.