From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Wang ShaoBo <bobo.shaobowang@huawei.com>
Cc: linux-block@vger.kernel.org, axboe@kernel.dk,
lars.ellenberg@linbit.com, liwei391@huawei.com,
drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH v2 2/2] drbd: destroy workqueue when drbd device was freed
Date: Tue, 22 Nov 2022 13:01:52 +0100 [thread overview]
Message-ID: <feff21b0-e583-4df3-7c38-4990ee60c3e4@linbit.com> (raw)
In-Reply-To: <20221122030427.731308-3-bobo.shaobowang@huawei.com>
Am 22.11.22 um 04:04 schrieb Wang ShaoBo:
> A submitter workqueue is dynamically allocated by init_submitter()
> called by drbd_create_device(), we should destroy it when this
> device is not needed or destroyed.
>
> Fixes: 113fef9e20e0 ("drbd: prepare to queue write requests on a submit worker")
> Signed-off-by: Wang ShaoBo <bobo.shaobowang@huawei.com>
> ---
> drivers/block/drbd/drbd_main.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/block/drbd/drbd_main.c b/drivers/block/drbd/drbd_main.c
> index 78cae4e75af1..2d6b6d1c5ff4 100644
> --- a/drivers/block/drbd/drbd_main.c
> +++ b/drivers/block/drbd/drbd_main.c
> @@ -2217,6 +2217,8 @@ void drbd_destroy_device(struct kref *kref)
> kref_put(&peer_device->connection->kref, drbd_destroy_connection);
> kfree(peer_device);
> }
> + if (device->submit.wq)
> + destroy_workqueue(device->submit.wq);
> kfree(device);
> kref_put(&resource->kref, drbd_destroy_resource);
> }
> @@ -2807,6 +2809,8 @@ enum drbd_ret_code drbd_create_device(struct drbd_config_context *adm_ctx, unsig
> put_disk(disk);
> out_no_disk:
> kref_put(&resource->kref, drbd_destroy_resource);
> + if (device->submit.wq)
> + destroy_workqueue(device->submit.wq);
> kfree(device);
> return err;
> }
Thanks, that is better.
Just one more nitpick: in drbd_create_device, we usually order the
allocations/frees in a "last in, first out" fashion. That is, data
should be released in the reverse order that it was allocated. This also
helps with error handling, which is what the out_* labels are used for.
So maybe we can put that destroy_workqueue() under its own out_* label
and make sure it gets freed first in the cleanup section (since it gets
allocated last).
--
Christoph Böhmwalder
LINBIT | Keeping the Digital World Running
DRBD HA — Disaster Recovery — Software defined Storage
prev parent reply other threads:[~2022-11-22 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 3:04 [Drbd-dev] [PATCH v2 0/2] drbd bugfix and cleanup Wang ShaoBo
2022-11-22 3:04 ` [Drbd-dev] [PATCH v2 1/2] drbd: remove call to memset before free device/resource/connection Wang ShaoBo
2022-11-22 3:04 ` [Drbd-dev] [PATCH v2 2/2] drbd: destroy workqueue when drbd device was freed Wang ShaoBo
2022-11-22 12:01 ` Christoph Böhmwalder [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=feff21b0-e583-4df3-7c38-4990ee60c3e4@linbit.com \
--to=christoph.boehmwalder@linbit.com \
--cc=axboe@kernel.dk \
--cc=bobo.shaobowang@huawei.com \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=liwei391@huawei.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