BPF List
 help / color / mirror / Atom feed
From: Tao Cui <cui.tao@linux.dev>
To: sashiko-reviews@lists.linux.dev
Cc: cui.tao@linux.dev, mkoutny@suse.com, tj@kernel.org,
	bpf@vger.kernel.org, hannes@cmpxchg.org
Subject: Re: [RFC PATCH v8 1/4] blk-iocost: add BPF struct_ops cost model support
Date: Wed, 30 Sep 2026 19:50:46 +0800	[thread overview]
Message-ID: <dbc80af8-f277-4180-bfe3-c7a56c265e8d@linux.dev> (raw)
In-Reply-To: <20260930081123.8CDA91F00893@smtp.kernel.org>

Hello,

在 2026/9/30 16:11, sashiko-bot@kernel.org 写道:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] block: Use-After-Free in q_to_ioc() list traversal due to dropped rq_qos_mutex
> --

The findings are confirmed; here is
how each will be addressed in the next revision:

1. Lockless q_to_ioc() in the attach path (sashiko, patch 1).

   Confirmed. After blk_iocost_init() succeeds, the attach path called
   q_to_ioc() with rq_qos_mutex released. Although the returned value was
   not used, q_to_ioc() walks the non-RCU rq_qos list and should not be
   called outside its synchronization. The unnecessary lookup is removed.

2. Missing test__skip() on -EOPNOTSUPP (sashiko, patch 2).

   Confirmed. Both attach paths now call test__skip() before returning so
   skipped tests are reported correctly. The unused line[256]/word[256]
   arrays in write_cost_model() are removed as well.

3. Documentation commit message vs. text (bpf-ci, patch 4).

   Confirmed. The commit message described two behaviors that were not
   stated explicitly in the documentation. The documentation is extended
   to say that detaching restores the builtin model, and that the ctrl
   field accepts only "auto" and "user" and never selects the active
   model.

Thanks,
Tao


  reply	other threads:[~2026-09-30 11:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  7:51 [RFC PATCH v8 0/4] blk-iocost: add BPF struct_ops cost model support Tao Cui
2026-09-30  7:51 ` [RFC PATCH v8 1/4] " Tao Cui
2026-09-30  8:11   ` sashiko-bot
2026-09-30 11:50     ` Tao Cui [this message]
2026-10-01  0:20   ` Tejun Heo
2026-10-02 14:17     ` Tao Cui
2026-09-30  7:51 ` [RFC PATCH v8 2/4] selftests/bpf: add iocost cost model test Tao Cui
2026-09-30  8:02   ` sashiko-bot
2026-10-01  0:20   ` Tejun Heo
2026-10-02 14:20     ` Tao Cui
2026-09-30  7:51 ` [RFC PATCH v8 3/4] blk-iocost: add iocost_ioc_tick tracepoint for per-period device summary Tao Cui
2026-10-01  0:20   ` Tejun Heo
2026-10-02 14:22     ` Tao Cui
2026-09-30  7:51 ` [RFC PATCH v8 4/4] docs: cgroup-v2: document the iocost BPF cost model attachment Tao Cui
2026-09-30  8:45   ` bot+bpf-ci
2026-10-01  0:20   ` Tejun Heo
2026-10-02 14:23     ` Tao Cui

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=dbc80af8-f277-4180-bfe3-c7a56c265e8d@linux.dev \
    --to=cui.tao@linux.dev \
    --cc=bpf@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=mkoutny@suse.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tj@kernel.org \
    /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