From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>, Uday Shankar <ushankar@purestorage.com>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH] ublk: set_params: properly check if parameters can be applied
Date: Wed, 05 Mar 2025 07:45:24 -0700 [thread overview]
Message-ID: <174118592485.8596.3723770986875822816.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250304-set_params-v1-1-17b5e0887606@purestorage.com>
On Tue, 04 Mar 2025 14:34:26 -0700, Uday Shankar wrote:
> The parameters set by the set_params call are only applied to the block
> device in the start_dev call. So if a device has already been started, a
> subsequently issued set_params on that device will not have the desired
> effect, and should return an error. There is an existing check for this
> - set_params fails on devices in the LIVE state. But this check is not
> sufficient to cover the recovery case. In this case, the device will be
> in the QUIESCED or FAIL_IO states, so set_params will succeed. But this
> success is misleading, because the parameters will not be applied, since
> the device has already been started (by a previous ublk server). The bit
> UB_STATE_USED is set on completion of the start_dev; use it to detect
> and fail set_params commands which arrive too late to be applied (after
> start_dev).
>
> [...]
Applied, thanks!
[1/1] ublk: set_params: properly check if parameters can be applied
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-03-05 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 21:34 [PATCH] ublk: set_params: properly check if parameters can be applied Uday Shankar
2025-03-05 2:34 ` Ming Lei
2025-03-05 14:45 ` Jens Axboe [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=174118592485.8596.3723770986875822816.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=ushankar@purestorage.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