[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4cea85d-e0d9-4926-f103-f29dd19e7b92@yandex.ru>
Date: Tue, 27 Jun 2023 21:30:07 +0500
From: stsp <stsp2@...dex.ru>
To: Jeff Layton <jlayton@...nel.org>, linux-kernel@...r.kernel.org
Cc: Chuck Lever <chuck.lever@...cle.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
linux-fsdevel@...r.kernel.org, Shuah Khan <shuah@...nel.org>,
linux-kselftest@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH 0/2] v3: F_OFD_GETLK extension to read lock info
27.06.2023 21:23, Jeff Layton пишет:
> I've taken the first two patches into my locks-next branch, so they
> should end up in linux-next soon. Adding support for testing this to
> fstests is a hard requirement before this will be merged into mainline.
Yes, it is _hard_...
I am still trying to set up the buildroot
environment for these tests:
https://bugs.busybox.net/show_bug.cgi?id=15665
And this will take some time, if at all
successful.
Additionally, these tests simply compare
the output with the pre-defined textual
patterns, so I have no idea what to do
after I figured "this feature is unsupported
on this kernel".
I sketched the tests, but the above problems
are holding things.
Powered by blists - more mailing lists