From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: linuxtestproject.agent@gmail.com
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lapi/prctl: add more fallback definitions
Date: Tue, 04 Aug 2026 07:39:50 +0000 [thread overview]
Message-ID: <6a719746.c69142e7.53fee.2bc3@mx.google.com> (raw)
In-Reply-To: <20260803143824.9095-1-linuxtestproject.agent@gmail.com>
> > +#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.
I'm having issues with this, since it seems struct prctl_mm_map gate it not
enough to ensure fallback is not replicating the original one.
> > + 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?
We don't support this kernel. Agent is going really deep with this, so I
guess I need to add a rule to avoid checking for versions below 4.4.
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-04 7:40 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 ` [LTP] " linuxtestproject.agent
2026-08-04 7:39 ` Andrea Cervesato via ltp [this message]
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=6a719746.c69142e7.53fee.2bc3@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=linuxtestproject.agent@gmail.com \
/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