mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tao Cui <cui.tao@linux.dev>
To: Kunhai Dai <daikunhai@didiglobal.com>, tj@kernel.org
Cc: cui.tao@linux.dev, axboe@kernel.dk, josef@toxicpanda.com,
	yukuai@fygo.io, cgroups@vger.kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] blk-iocost: fix hweight cache publication and donation fail-safe
Date: Tue, 20 Oct 2026 17:16:20 +0800	[thread overview]
Message-ID: <6e7d6232-d422-47f3-bc85-a52508cb172f@linux.dev> (raw)
In-Reply-To: <20261019125412.3123895-1-daikunhai@didiglobal.com>

Hi Kunhai,

在 2026/10/19 20:54, Kunhai Dai 写道:
> This series fixes the blk-iocost hweight cache publication race and adds a
> fail-safe for invalid donation weights.
> 
> Previous version:
>   https://lists.openwall.net/linux-kernel/2026/10/15/1954
> Replies:
>   https://lists.openwall.net/linux-kernel/2026/10/16/1431
>   https://lists.openwall.net/linux-kernel/2026/10/16/2798

I re-ran the injection tests on my side (linux-next 20261019):
two runs with a 30ms kprobe
hold on every refresh of current_hweight() and one with the hold on every
50th refresh, same rt/s1..C topology and 1 <-> 10000 weight alternation
load as before. No WARN or oops, and the tracepoint hweight fields decoded
within [1, 65536] in every run.

For the series:

Tested-by: Tao Cui <cuitao@kylinos.cn>
Reviewed-by: Tao Cui <cuitao@kylinos.cn>

Thanks,
Tao

      parent reply	other threads:[~2026-10-20  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 12:54 Kunhai Dai
2026-10-19 12:54 ` [PATCH v2 1/2] blk-iocost: abort weight transfer on invalid donation weights Kunhai Dai
2026-10-19 12:54 ` [PATCH v2 2/2] blk-iocost: publish hweights as one atomic value Kunhai Dai
2026-10-19 23:12 ` [PATCH v2 0/2] blk-iocost: fix hweight cache publication and donation fail-safe Tejun Heo
2026-10-20  9:16 ` Tao Cui [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=6e7d6232-d422-47f3-bc85-a52508cb172f@linux.dev \
    --to=cui.tao@linux.dev \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=daikunhai@didiglobal.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tj@kernel.org \
    --cc=yukuai@fygo.io \
    /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®