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 v3 1/2] drbd: remove call to memset before free device/resource/connection
Date: Wed, 23 Nov 2022 11:16:00 +0100 [thread overview]
Message-ID: <7d972801-148a-87b2-9fe1-9992b943916f@linbit.com> (raw)
In-Reply-To: <20221123020355.2470160-2-bobo.shaobowang@huawei.com>
Am 23.11.22 um 03:03 schrieb Wang ShaoBo:
> This revert c2258ffc56f2 ("drbd: poison free'd device, resource and
> connection structs"), add memset is odd here for debugging, there are
> some methods to accurately show what happened, such as kdump.
>
> Signed-off-by: Wang ShaoBo <bobo.shaobowang@huawei.com>
> ---
> drivers/block/drbd/drbd_main.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/block/drbd/drbd_main.c b/drivers/block/drbd/drbd_main.c
> index 8532b839a343..78cae4e75af1 100644
> --- a/drivers/block/drbd/drbd_main.c
> +++ b/drivers/block/drbd/drbd_main.c
> @@ -2217,7 +2217,6 @@ void drbd_destroy_device(struct kref *kref)
> kref_put(&peer_device->connection->kref, drbd_destroy_connection);
> kfree(peer_device);
> }
> - memset(device, 0xfd, sizeof(*device));
> kfree(device);
> kref_put(&resource->kref, drbd_destroy_resource);
> }
> @@ -2309,7 +2308,6 @@ void drbd_destroy_resource(struct kref *kref)
> idr_destroy(&resource->devices);
> free_cpumask_var(resource->cpu_mask);
> kfree(resource->name);
> - memset(resource, 0xf2, sizeof(*resource));
> kfree(resource);
> }
>
> @@ -2650,7 +2648,6 @@ void drbd_destroy_connection(struct kref *kref)
> drbd_free_socket(&connection->data);
> kfree(connection->int_dig_in);
> kfree(connection->int_dig_vv);
> - memset(connection, 0xfc, sizeof(*connection));
> kfree(connection);
> kref_put(&resource->kref, drbd_destroy_resource);
> }
Thanks!
Acked-by: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>
--
Christoph Böhmwalder
LINBIT | Keeping the Digital World Running
DRBD HA — Disaster Recovery — Software defined Storage
next prev parent reply other threads:[~2022-11-23 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 2:03 [Drbd-dev] [PATCH v3 0/2] drbd bugfix and cleanup Wang ShaoBo
2022-11-23 2:03 ` [Drbd-dev] [PATCH v3 1/2] drbd: remove call to memset before free device/resource/connection Wang ShaoBo
2022-11-23 10:16 ` Christoph Böhmwalder [this message]
2022-11-23 2:03 ` [Drbd-dev] [PATCH v3 2/2] drbd: destroy workqueue when drbd device was freed Wang ShaoBo
2022-11-23 10:16 ` Christoph Böhmwalder
2022-11-23 13:49 ` [Drbd-dev] [PATCH v3 0/2] drbd bugfix and cleanup 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=7d972801-148a-87b2-9fe1-9992b943916f@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