All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 2/2] cve: add test reproducer for cve-2025-21756
Date: Tue, 23 Sep 2025 14:16:45 +0200	[thread overview]
Message-ID: <aNKPrUbjC3-oftGI@yuki.lan> (raw)
In-Reply-To: <87878992-ee9a-48a3-93a5-7e38bcd65bc1@suse.com>

Hi!
> > So this generally works all the way back to the oldest LTP supported
> > kernel? I would expect that we would need an EINVAL check here.
> 
> AF_VSOCK were defined in 3.10 (d021c344051a VSOCK: Introduce VM 
> Sockets), so I guess we are pretty safe.

Ack.

> Should I merge it after the Review-by, or we should wait for the release?

As long as it passes the compilation CI I would be inclined to take it
in. The pros is that we get one more CVE reproducer and the cons are
that we add one buggy test, it shouldn't break more than that.

However that should be the last non-fix before the release.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2025-09-23 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23  8:40 [LTP] [PATCH v2 0/2] cve-2025-21756 reproducer Andrea Cervesato
2025-09-23  8:40 ` [LTP] [PATCH v2 1/2] lapi: add struct sockaddr_vm fallback Andrea Cervesato
2025-09-23 11:52   ` Cyril Hrubis
2025-09-23  8:41 ` [LTP] [PATCH v2 2/2] cve: add test reproducer for cve-2025-21756 Andrea Cervesato
2025-09-23 11:55   ` Cyril Hrubis
2025-09-23 12:09     ` Andrea Cervesato via ltp
2025-09-23 12:16       ` Cyril Hrubis [this message]
2025-09-23 13:28         ` 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=aNKPrUbjC3-oftGI@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --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.