All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 27 Aug 2026 08:51:06 +0000	[thread overview]
Message-ID: <6a8ffa7a.ed0817e7.d5305.0f1b@mx.google.com> (raw)
In-Reply-To: <20260827083636.8672-1-linuxtestproject.agent@gmail.com>

> > +static struct tst_test test = {
> > +	.setup = setup,
> > +	.test_all = run,
> > +	.runtime = 180,
> 
> Could this declare .min_kver = "3.18", or otherwise treat EINVAL from
> PR_SET_MM_MAP_SIZE as an unavailable prerequisite? PR_SET_MM_MAP was added in
> Linux 3.18, while the CVE affects older kernels. On such a kernel,
> SAFE_PRCTL() currently reports TBROK rather than TCONF.
> 
> >  cve-2014-0196 cve-2016-7117 cve-2017-2671 cve-2017-17052 cve-2017-17053 refluxfs:  CFLAGS += -pthread
> > +cve-2014-0196 cve-2016-7117 cve-2017-2671 cve-2017-17052 cve-2017-17053 ghostlock:  CFLAGS += -pthread
> 
> Could ghostlock be added to the existing assignment instead? The new line
> passes -pthread twice to every pre-existing target listed there.
> 
> >  refluxfs
> >  sctphantom
> > +ghostlock
> 
> Could ghostlock be inserted in sorted order?

only these two are valid, the rest can be ignored.

--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com

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

  reply	other threads:[~2026-08-27  8:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 12:40 [LTP] [PATCH v4 0/2] Reproducer for ghostlock Andrea Cervesato
2026-08-26 12:40 ` [LTP] [PATCH v4 1/2] lapi/prctl: add more fallback definitions Andrea Cervesato
2026-08-27  8:36   ` [LTP] " linuxtestproject.agent
2026-08-27  8:51     ` Andrea Cervesato via ltp [this message]
2026-08-26 12:40 ` [LTP] [PATCH v4 2/2] cve: add CVE-2026-43499 reproducer Andrea Cervesato
2026-09-01  8:36   ` Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
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
2026-08-03  8:10 [LTP] [PATCH v2 1/2] " 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=6a8ffa7a.ed0817e7.d5305.0f1b@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 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.