From: Uday Shankar <ushankar@purestorage.com>
To: Yoav Cohen <yoav@nvidia.com>
Cc: Ming Lei <ming.lei@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: ublk: Graceful Upgrade of ublk server application
Date: Tue, 15 Apr 2025 18:51:57 -0600 [thread overview]
Message-ID: <Z/7/LTSxqLH7JgAl@dev-ushankar.dev.purestorage.com> (raw)
In-Reply-To: <DM4PR12MB63285A6617D8A9B9F22B912BA9B22@DM4PR12MB6328.namprd12.prod.outlook.com>
On Tue, Apr 15, 2025 at 07:46:51PM +0000, Yoav Cohen wrote:
> Hi Ming,
>
> Thank you for the fast reply.
> To be clear, I don't want calling DELETE_DEV or STOP_DEV as I want the kernel bdev will be stay while upgrading the ublk server application.
> It would be nice to have a nice way to have something like FREEZE_DEV that we may use which will also make all the cmds back with ABORT result but both block and char device will be stay until a new userspace application will reconnect.
Have you taken a look at the recovery flags? These offer slightly
different behaviors around how I/O is handled while the ublk server is
dying/when it is dead, but they all keep the block device up even after
the ublk server exits.
The flags are documented at https://docs.kernel.org/block/ublk.html
next prev parent reply other threads:[~2025-04-16 0:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 8:15 ublk: Graceful Upgrade of ublk server application Yoav Cohen
2025-04-15 11:06 ` Ming Lei
2025-04-15 19:46 ` Yoav Cohen
2025-04-16 0:51 ` Uday Shankar [this message]
2025-04-16 1:39 ` Ming Lei
2025-04-16 8:16 ` Yoav Cohen
2025-04-16 9:12 ` Ming Lei
2025-04-20 8:57 ` Yoav Cohen
2025-04-21 2:43 ` Ming Lei
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=Z/7/LTSxqLH7JgAl@dev-ushankar.dev.purestorage.com \
--to=ushankar@purestorage.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=yoav@nvidia.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.