All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Hui Su <sh_def@163.com>
Cc: sched-ext@lists.linux.dev, void@manifault.com, arighi@nvidia.com,
	changwoo@igalia.com, mingo@redhat.com, peterz@infradead.org,
	juri.lelli@redhat.com, vincent.guittot@linaro.org,
	dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
	kprateek.nayak@amd.com, yphbchou0911@gmail.com, etsal@meta.com,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] sched_ext: Serialize user DSQ destruction against deferred reenqueues
Date: Fri, 09 Oct 2026 12:01:46 -1000	[thread overview]
Message-ID: <6782b5c7b47824ce6a89c506cca1186b@kernel.org> (raw)
In-Reply-To: <20261008024753.4096008-1-sh_def@163.com>

Hello, Hui.

On Thu, Oct 08, 2026 at 11:47:53AM +0900, Hui Su wrote:
> After the initial grace period, take every rq lock with its deferred lock.
> This unlinks requests not yet detached and closes the detach-to-cursor
> window for active consumers. reenq_user() leaves its iteration cursor on

I'd rather cancel the pending requests before the grace period, so that
exit_dsq()'s assumption holds and its WARN keeps catching lost schedules:

  https://lore.kernel.org/all/20261009220001.196762128-1-tj@kernel.org/

Can you test that one instead?

Thanks.

-- 
tejun

      reply	other threads:[~2026-10-09 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  2:47 [PATCH v3] sched_ext: Serialize user DSQ destruction against deferred reenqueues Hui Su
2026-10-09 22:01 ` Tejun Heo [this message]

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=6782b5c7b47824ce6a89c506cca1186b@kernel.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=bsegall@google.com \
    --cc=changwoo@igalia.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=etsal@meta.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sched-ext@lists.linux.dev \
    --cc=sh_def@163.com \
    --cc=stable@vger.kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=void@manifault.com \
    --cc=vschneid@redhat.com \
    --cc=yphbchou0911@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.