From: "Wangshaobo (bobo)" <bobo.shaobowang@huawei.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: <liwei391@huawei.com>, <linux-block@vger.kernel.org>,
<drbd-dev@lists.linbit.com>, <christoph.boehmwalder@linbit.com>
Subject: Re: [RESEND PATCH] drbd: destroy workqueue when drbd device was freed
Date: Tue, 22 Nov 2022 11:08:00 +0800 [thread overview]
Message-ID: <5b3ff507-7cc7-cb9d-1c9c-f497cb19cafb@huawei.com> (raw)
In-Reply-To: <c0e639ea-caa0-f76c-c369-0d22a49047ca@kernel.dk>
在 2022/11/21 22:30, Jens Axboe 写道:
> On 11/21/22 4:50 AM, Wang ShaoBo wrote:
>> 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>
>> ---
>>
>> Changes in RESEND:
>> put destroy_workqueue() before memset(device, ...)
>>
>> drivers/block/drbd/drbd_main.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/block/drbd/drbd_main.c b/drivers/block/drbd/drbd_main.c
>> index 8532b839a343..082bc34cd317 100644
>> --- a/drivers/block/drbd/drbd_main.c
>> +++ b/drivers/block/drbd/drbd_main.c
>> @@ -2217,7 +2217,12 @@ 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);
>> +
>> memset(device, 0xfd, sizeof(*device));
>> +
>> kfree(device);
> Maybe you can send a separate patch killing that very odd (and useless)
> memset as well?
I have sent v2 version adding a new patch for killing that memset.^-^
-- Wang ShaoBo
prev parent reply other threads:[~2022-11-22 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 11:50 [RESEND PATCH] drbd: destroy workqueue when drbd device was freed Wang ShaoBo
2022-11-21 14:30 ` Jens Axboe
2022-11-22 3:08 ` Wangshaobo (bobo) [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=5b3ff507-7cc7-cb9d-1c9c-f497cb19cafb@huawei.com \
--to=bobo.shaobowang@huawei.com \
--cc=axboe@kernel.dk \
--cc=christoph.boehmwalder@linbit.com \
--cc=drbd-dev@lists.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