From: Mark Harmstone <maharmstone@meta.com>
To: Zorro Lang <zlang@redhat.com>
Cc: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"zlang@kernel.org" <zlang@kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: add test for encoded reads
Date: Wed, 20 Nov 2024 16:14:08 +0000 [thread overview]
Message-ID: <bbeea4ec-2f77-47fd-ab5c-6319d4248496@meta.com> (raw)
In-Reply-To: <20241114050631.x3urk2ti4ukgtaai@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On 14/11/24 05:06, Zorro Lang wrote:
...
>> It looks like IORING_OP_URING_CMD was added to liburing with version
>> 2.2, which came out in June 2022. I don't know whether that's old enough
>> that we can just declare it as our minimum version, whether we should be
>> probing for the liburing version, whether we should be working round
>> this somehow, or what.
>>
>> Zorro, what do you think?
>
> 2022 was just 2 years ago, some downstream distributions might use old version.
> I think that might be too early to leave a "2 years ago" system out of the using of
> latest xfstests :)
>
> Thanks,
> Zorro
Okay, no worries. I can change it so that it uses the raw syscalls
rather than the liburing helpers. It'll be a lot uglier, but at least
it'll work.
Johannes, what distro and version are you on? I'll make sure it works on
that.
Mark
next prev parent reply other threads:[~2024-11-20 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 14:55 [PATCH] btrfs: add test for encoded reads Mark Harmstone
2024-11-12 9:37 ` Johannes Thumshirn
2024-11-13 12:28 ` Mark Harmstone
2024-11-14 5:06 ` Zorro Lang
2024-11-20 16:14 ` Mark Harmstone [this message]
2024-11-20 16:31 ` Johannes Thumshirn
2024-11-21 4:43 ` Anand Jain
2024-11-12 9:47 ` Johannes Thumshirn
2024-11-12 15:23 ` Mark Harmstone
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=bbeea4ec-2f77-47fd-ab5c-6319d4248496@meta.com \
--to=maharmstone@meta.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=zlang@kernel.org \
--cc=zlang@redhat.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