From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Martin Doucha <martin.doucha@suse.com>,
ltp@lists.linux.it, linuxtestproject.agent@gmail.com
Subject: Re: [LTP] cve: add pwnescape reproducer
Date: Thu, 5 Nov 2026 11:50:23 +0100 [thread overview]
Message-ID: <20261105105023.GA459386@pevik> (raw)
In-Reply-To: <oB4QkHztnNTcZNqTMjoGQkygrRUmUoyoYwsG@localhost.localdomain>
Hi Andrea, all,
I'm verifying it at least on some of SLES versions.
FYI on 4.12 and 4.4 based SLES kernels with backported 6785011f8b16 (i.e. fixed
kernels) the test fails:
pwnescape.c:213: TBROK: control datagram was not forwarded back
=> obviously test is not working on older codestreams, that would be good to get
fixed. I try to have look on it, but I'm not sure if I manage it till the end of
the month.
Otherwise LGTM, thanks!
Reviewed-by: Petr Vorel <pvorel@suse.cz>
> > Hi Andrea,
> > On Tue, 20 Oct 2026, Andrea Cervesato wrote:
> > > cve: add pwnescape reproducer
> > > + .tags = (const struct tst_tag[]) {
> > > + {"linux-git", "6785011f8b16"},
> > > + {}
> > > + },
> > Add {"CVE", "2026-99999"} to .tags in testcases/cve/pwnescape.c.
> > Without it, metadata extraction assigns only the regression group, so
> > CVE-based metadata selection and the generated CVE catalog omit this test;
> > the runtest/cve entry does not populate that metadata.
> Valid, I will fix it before merge
Sure, I can add it before merge.
> > Runtime verification was blocked by unshare(CLONE_NEWUSER) returning
> > EPERM in this environment, before the forwarding behavior was exercised.
> This is the github LSM pushing out the reproducer. It's not a test bug
Sure.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-11-05 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 16:22 [LTP] [PATCH v2] cve: add pwnescape reproducer Andrea Cervesato
2026-10-20 19:01 ` [LTP] " linuxtestproject.agent
2026-10-21 8:01 ` Andrea Cervesato via ltp
2026-11-05 10:50 ` Petr Vorel [this message]
2026-11-05 17:17 ` Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2026-10-20 13:59 [LTP] [PATCH] " Andrea Cervesato
2026-10-20 14:51 ` [LTP] " linuxtestproject.agent
2026-10-20 16:22 ` Andrea Cervesato via ltp
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=20261105105023.GA459386@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.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