From: Stas Sergeev <stsp2@yandex.ru>
To: fstests@vger.kernel.org
Cc: Stas Sergeev <stsp2@yandex.ru>, Murphy Zhou <xzhou@redhat.com>,
Jeff Layton <jlayton@kernel.org>, Zorro Lang <zlang@redhat.com>
Subject: [PATCH v3 0/2] t_ofd_locks: ipc semaphore fixes
Date: Tue, 1 Aug 2023 22:52:18 +0500 [thread overview]
Message-ID: <20230801175220.1558342-1-stsp2@yandex.ru> (raw)
This patch set provides 2 semaphore fixes for t_ofd_locks.
First patch fixes the handling of stalled semaphore.
Second patch fixes the init sequence, making sure the lock-setter
process actually waits for the lock-getter to initialize.
Changes in v3: sem is now created by the wrapper script, rather than
by the lock-setter process. This allowed to remove the sem-await loop
from the lock-getter, speeding up the test ~5 times.
CC: fstests@vger.kernel.org
CC: Murphy Zhou <xzhou@redhat.com>
CC: Jeff Layton <jlayton@kernel.org>
CC: Zorro Lang <zlang@redhat.com>
Signed-off-by: Stas Sergeev <stsp2@yandex.ru>
Stas Sergeev (2):
t_ofd_locks: fix stalled semaphore handling
t_ofd_locks: fix sem initialization sequence
src/t_ofd_locks.c | 92 +++++++++++++++++++----------------------------
tests/generic/478 | 14 +++++---
2 files changed, 47 insertions(+), 59 deletions(-)
--
2.39.2
next reply other threads:[~2023-08-01 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 17:52 Stas Sergeev [this message]
2023-08-01 17:52 ` [PATCH 1/2] t_ofd_locks: fix stalled semaphore handling Stas Sergeev
2023-08-11 11:39 ` Jeff Layton
2023-08-11 11:53 ` stsp
2023-08-01 17:52 ` [PATCH 2/2] t_ofd_locks: fix sem initialization sequence Stas Sergeev
2023-08-11 11:51 ` Jeff Layton
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=20230801175220.1558342-1-stsp2@yandex.ru \
--to=stsp2@yandex.ru \
--cc=fstests@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=xzhou@redhat.com \
--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