From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Caleb Sander Mateos <csander@purestorage.com>,
Uday Shankar <ushankar@purestorage.com>,
Seamus Connor <sconnor@purestorage.com>,
Ming Lei <ming.lei@redhat.com>
Subject: [PATCH 2/2] selftests/ublk: fix garbage output and cleanup on failure
Date: Mon, 12 Jan 2026 12:12:06 +0800 [thread overview]
Message-ID: <20260112041209.79445-3-ming.lei@redhat.com> (raw)
In-Reply-To: <20260112041209.79445-1-ming.lei@redhat.com>
Fix several issues in kublk:
1. Initialize _evtfd to -1 in struct dev_ctx to prevent garbage output
in foreground mode. Without this, _evtfd is zero-initialized to 0
(stdin), and when ublk_send_dev_event() is called on failure, it
writes binary data to stdin which appears as garbage on the terminal.
2. Move fail label in ublk_start_daemon() to ensure pthread_join() is
called before queue deinit on the error path. This ensures proper
thread cleanup when startup fails.
3. Add async parameter to ublk_ctrl_del_dev() and use async deletion
when the daemon fails to start. This prevents potential hangs when
deleting a device that failed during startup.
Also fix a debug message format string that was missing __func__ and
had wrong escape character.
Fixes: 6aecda00b7d1 ("selftests: ublk: add kernel selftests for ublk")
Signed-off-by: Ming Lei <ming.lei@redhat.com>
---
tools/testing/selftests/ublk/kublk.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/tools/testing/selftests/ublk/kublk.c b/tools/testing/selftests/ublk/kublk.c
index 185ba553686a..0c62a967f2cb 100644
--- a/tools/testing/selftests/ublk/kublk.c
+++ b/tools/testing/selftests/ublk/kublk.c
@@ -153,11 +153,10 @@ static int ublk_ctrl_add_dev(struct ublk_dev *dev)
return __ublk_ctrl_cmd(dev, &data);
}
-static int ublk_ctrl_del_dev(struct ublk_dev *dev)
+static int ublk_ctrl_del_dev(struct ublk_dev *dev, bool async)
{
struct ublk_ctrl_cmd_data data = {
- .cmd_op = UBLK_U_CMD_DEL_DEV,
- .flags = 0,
+ .cmd_op = async ? UBLK_U_CMD_DEL_DEV_ASYNC: UBLK_U_CMD_DEL_DEV,
};
return __ublk_ctrl_cmd(dev, &data);
@@ -1063,11 +1062,11 @@ static int ublk_start_daemon(const struct dev_ctx *ctx, struct ublk_dev *dev)
else
ublk_send_dev_event(ctx, dev, dev->dev_info.dev_id);
+ fail:
/* wait until we are terminated */
for (i = 0; i < dev->nthreads; i++)
pthread_join(tinfo[i].thread, &thread_ret);
free(tinfo);
- fail:
for (i = 0; i < dinfo->nr_hw_queues; i++)
ublk_queue_deinit(&dev->q[i]);
ublk_dev_unprep(dev);
@@ -1272,9 +1271,9 @@ static int __cmd_dev_add(const struct dev_ctx *ctx)
}
ret = ublk_start_daemon(ctx, dev);
- ublk_dbg(UBLK_DBG_DEV, "%s: daemon exit %d\b", ret);
+ ublk_dbg(UBLK_DBG_DEV, "%s: daemon exit %d\n", __func__, ret);
if (ret < 0)
- ublk_ctrl_del_dev(dev);
+ ublk_ctrl_del_dev(dev, true);
fail:
if (ret < 0)
@@ -1371,7 +1370,7 @@ static int __cmd_dev_del(struct dev_ctx *ctx)
if (ret < 0)
ublk_err("%s: stop daemon id %d dev %d, ret %d\n",
__func__, dev->dev_info.ublksrv_pid, number, ret);
- ublk_ctrl_del_dev(dev);
+ ublk_ctrl_del_dev(dev, false);
fail:
ublk_ctrl_deinit(dev);
@@ -1622,6 +1621,7 @@ int main(int argc, char *argv[])
.nr_hw_queues = 2,
.dev_id = -1,
.tgt_type = "unknown",
+ ._evtfd = -1,
};
int ret = -EINVAL, i;
int tgt_argc = 1;
--
2.47.0
next prev parent reply other threads:[~2026-01-12 4:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 4:12 [PATCH 0/2] ublk: fix error handling if start_dev pid validation failed Ming Lei
2026-01-12 4:12 ` [PATCH 1/2] ublk: cancel device on START_DEV failure Ming Lei
2026-01-12 16:52 ` Caleb Sander Mateos
2026-01-13 1:38 ` Ming Lei
2026-01-12 4:12 ` Ming Lei [this message]
2026-01-12 17:36 ` [PATCH 2/2] selftests/ublk: fix garbage output and cleanup on failure Caleb Sander Mateos
2026-01-13 1:46 ` Ming Lei
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=20260112041209.79445-3-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=linux-block@vger.kernel.org \
--cc=sconnor@purestorage.com \
--cc=ushankar@purestorage.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