From: Kuba Piecuch <jpiecuch@google.com>
To: sashiko-bot@kernel.org
Cc: Kuba Piecuch <jpiecuch@google.com>, sched-ext@lists.linux.dev
Subject: Re: [PATCH 1/3] selftests/sched_ext: Add a test for ops.dequeue() on remote local DSQ moves
Date: Wed, 30 Sep 2026 11:50:42 +0000 [thread overview]
Message-ID: <20260930115044.337291-4-jpiecuch@google.com> (raw)
In-Reply-To: <20260929162803.B33D01F000FF@smtp.kernel.org>
On Tue, Sep 29, 2026 at 04:28:03PM +0000, sashiko-bot@kernel.org wrote:
> Could the test be updated to use a goto cleanup path, or perhaps assign the
> link to the skeleton so it is destroyed automatically, ensuring it doesn't
> block subsequent tests on error?
Good catch. In v2, run_scenario() always destroys the link once it's
attached. If fork() or waitpid() fails, it also kills and reaps the
workers it has already forked.
Thanks,
Kuba
next prev parent reply other threads:[~2026-09-30 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 16:17 [PATCHSET sched_ext/for-7.3-fixes] sched_ext: Fix missing ops.dequeue() on remote local DSQ moves Kuba Piecuch
2026-09-29 16:17 ` [PATCH 1/3] selftests/sched_ext: Add a test for " Kuba Piecuch
2026-09-29 16:28 ` sashiko-bot
2026-09-30 11:50 ` Kuba Piecuch [this message]
2026-09-29 18:42 ` Andrea Righi
2026-09-30 11:50 ` Kuba Piecuch
2026-09-29 16:17 ` [PATCH 2/3] sched_ext: Call ops.dequeue() when a task arrives on a remote local DSQ Kuba Piecuch
2026-09-29 18:33 ` Andrea Righi
2026-09-30 11:50 ` Kuba Piecuch
2026-09-29 16:17 ` [PATCH 3/3] selftests/sched_ext: Enable the dequeue_remote test Kuba Piecuch
2026-09-29 17:13 ` [PATCHSET sched_ext/for-7.3-fixes] sched_ext: Fix missing ops.dequeue() on remote local DSQ moves Tejun Heo
2026-09-29 18:30 ` Andrea Righi
2026-09-30 11:50 ` Kuba Piecuch
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=20260930115044.337291-4-jpiecuch@google.com \
--to=jpiecuch@google.com \
--cc=sashiko-bot@kernel.org \
--cc=sched-ext@lists.linux.dev \
/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