From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <shuah@kernel.org>, Jeff Layton <jlayton@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [PATCH v4 1/3] kselftest/filelock: Use ksft_perror()
Date: Thu, 26 Feb 2026 16:05:25 +0000 [thread overview]
Message-ID: <20260226-selftest-filelock-ktap-v4-1-db8ae192ff42@kernel.org> (raw)
In-Reply-To: <20260226-selftest-filelock-ktap-v4-0-db8ae192ff42@kernel.org>
The ofdlocks test reports some errors via perror() which does not produce
KTAP output, convert to ksft_perror() which does.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/filelock/ofdlocks.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/filelock/ofdlocks.c b/tools/testing/selftests/filelock/ofdlocks.c
index ff8d47fc373a..2d3b06ce5e5e 100644
--- a/tools/testing/selftests/filelock/ofdlocks.c
+++ b/tools/testing/selftests/filelock/ofdlocks.c
@@ -16,7 +16,7 @@ static int lock_set(int fd, struct flock *fl)
fl->l_whence = SEEK_SET;
ret = fcntl(fd, F_OFD_SETLK, fl);
if (ret)
- perror("fcntl()");
+ ksft_perror("fcntl()");
return ret;
}
@@ -28,7 +28,7 @@ static int lock_get(int fd, struct flock *fl)
fl->l_whence = SEEK_SET;
ret = fcntl(fd, F_OFD_GETLK, fl);
if (ret)
- perror("fcntl()");
+ ksft_perror("fcntl()");
return ret;
}
--
2.47.3
next prev parent reply other threads:[~2026-02-26 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 16:05 [PATCH v4 0/3] selftests/filelock: Make output more kselftestish Mark Brown
2026-02-26 16:05 ` Mark Brown [this message]
2026-02-26 16:05 ` [PATCH v4 2/3] kselftest/filelock: Report each test in oftlocks separately Mark Brown
2026-02-26 16:05 ` [PATCH v4 3/3] kselftest/filelock: Add a .gitignore file Mark Brown
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=20260226-selftest-filelock-ktap-v4-1-db8ae192ff42@kernel.org \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®