From: Daniel Wagner <dwagner@suse.de>
To: Bill Wendling <morbo@google.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Kees Cook <kees@kernel.org>,
Gogul Balakrishnan <bgogul@google.com>,
Arman Hasanzadeh <armanihm@google.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH] blkdev: Annotate struct request_queue with __counted_by_ptr
Date: Thu, 19 Feb 2026 18:23:58 +0100 [thread overview]
Message-ID: <e3c0a209-56f7-4ac2-b089-e0600672cf25@flourine.local> (raw)
In-Reply-To: <CAGG=3QXcA7et9LmZ+Cu8zn1yBXrPizL7BhYFvfFZpWA7aUR3xw@mail.gmail.com>
On Thu, Feb 19, 2026 at 09:02:12AM -0800, Bill Wendling wrote:
> It's normally fine to change the queue count just as long as either
> (1) the pointer to the queues is also reallocated, or (2) the count
> never goes over the original allocated value. (The second one is more
> difficult to check, of course.) The bounds safety features that Apple
> developed, and which are slowly being sent upstream, enforces (1).
>
> I'll run the other tests, but I'm not familiar with the blktests (I
> downloaded them but haven't looked too deeply into them). Do you have
> some pointers on how to run them with a newly built kernel?
blktests has feature detection and every tests figures out, if it can
run or not. It will print some info when it's not possible.
The block test suite has at least a couple related tests:
./check block/029 block/040
This suite wants null_blk driver.
And for nvme/048 the fabrics parts needs to be used:
NVMET_TRTYPES="tcp" ./check nvme/048
and the nvme-fabrics part nvme-tcp and nvmet-tcp.
If you need the exact config option I can compile you a list.
next prev parent reply other threads:[~2026-02-19 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 0:49 Bill Wendling
2026-02-19 12:14 ` Daniel Wagner
2026-02-19 17:02 ` Bill Wendling
2026-02-19 17:23 ` Daniel Wagner [this message]
2026-02-23 22:47 ` Bill Wendling
2026-02-24 8:55 ` Daniel Wagner
2026-02-25 18:26 ` Bill Wendling
2026-02-25 18:53 ` Jens Axboe
2026-02-25 19:00 ` Daniel Wagner
2026-02-25 20:45 ` Bill Wendling
2026-02-25 20:51 ` [PATCH v2] " Bill Wendling
2026-02-26 15:41 ` Jens Axboe
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=e3c0a209-56f7-4ac2-b089-e0600672cf25@flourine.local \
--to=dwagner@suse.de \
--cc=armanihm@google.com \
--cc=axboe@kernel.dk \
--cc=bgogul@google.com \
--cc=kees@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morbo@google.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
all inboxes | Powered by JetHome®