Linux Test Project
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: pvorel <pvorel@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v6] cve: reproducer for cve-2026-64600
Date: Fri, 07 Aug 2026 07:51:20 +0000	[thread overview]
Message-ID: <6a758e79.5fb1dcdd.355f96.e2e4@mx.google.com> (raw)
In-Reply-To: <a1d939127b54c51fd29f869b0fe1706f@suse.de>

Hi Petr,

> > +			.min_kver = "4.16",
> It got introduced in 4.11. Is there a reason for testing from 4.16?
> Or is it just the copy paste error?

1e369b0e199bb ("xfs: remove experimental tag for reflinks") was merged
in 4.16

> 
> Other than that LGTM.
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> 
> > +			.mkfs_ver = "mkfs.xfs >= 1.5.0",
> > +			.mkfs_opts = (const char *const []) {
> > +				"-m", "reflink=1",
> > +				NULL
> > +			},
> > +		},
> > +		{}
> > +	},
> > +	.tags = (const struct tst_tag[]) {
> > +		{"linux-git", "2f4acd0fcd86"},
> Can you please before merge use longer hash
> "2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7"?

I thought as a rule we always have to use short hash, we never use
longer one, besides a couple of tests. Is there a reason for it?

--
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-07  7:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  9:45 [LTP] [PATCH v6] cve: reproducer for cve-2026-64600 Andrea Cervesato
2026-08-06 10:41 ` [LTP] " linuxtestproject.agent
2026-08-07  7:35 ` [LTP] [PATCH v6] " pvorel
2026-08-07  7:51   ` Andrea Cervesato via ltp [this message]

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=6a758e79.5fb1dcdd.355f96.e2e4@mx.google.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.com \
    --cc=pvorel@suse.de \
    /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