From: Tejun Heo <htejun@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, Suman Anna <s-anna@ti.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-scsi@vger.kernel.org, open-iscsi@googlegroups.com
Subject: Re: DEFINE_IDA causing memory leaks? (was Re: [PATCH 1/2] virtio: fix memory leak of virtio ida cache layers)
Date: Thu, 17 Sep 2015 11:10:26 -0400 [thread overview]
Message-ID: <20150917151026.GB7205@mtj.duckdns.org> (raw)
In-Reply-To: <1442499344.4073.0.camel@HansenPartnership.com>
Hello,
On Thu, Sep 17, 2015 at 07:15:44AM -0700, James Bottomley wrote:
> I don't understand why you'd want to forbid DEFINE_IDA ... all it does
I guess to require the use of explicit init / creation so that it's
clear the data structure needs to be destroyed?
> is pre-initialise a usually static ida structure. The initialised
> structure will have a NULL bitmap cache that's allocated in the first
> ida_pre_get() ... that all seems to work as expected and no different
> from a dynamically allocated struct ida. Or are you thinking because
> ida_destory() doesn't set bitmap to NULL, it damages the reuse? In
> which case I'm not sure there's much benefit to making it reusable, but
> I suppose we could by adding a memset into ida_destroy().
I don't know. Data structures which do lazy anything would likely
need explicit destruction and I'm not sure we'd wanna ban static
initialization for all such cases. Seems like an unnecessary
restriction.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-09-17 15:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 0:29 [PATCH 0/2] Fix memory leaks in virtio & remoteproc cores Suman Anna
2015-09-17 0:29 ` [PATCH 1/2] virtio: fix memory leak of virtio ida cache layers Suman Anna
2015-09-17 5:33 ` DEFINE_IDA causing memory leaks? (was Re: [PATCH 1/2] virtio: fix memory leak of virtio ida cache layers) Michael S. Tsirkin
2015-09-17 6:51 ` Hannes Reinecke
2015-09-17 22:32 ` Suman Anna
2015-09-17 14:15 ` James Bottomley
2015-09-17 15:10 ` Tejun Heo [this message]
2015-09-17 16:06 ` Michael S. Tsirkin
2015-09-17 16:48 ` James Bottomley
2015-09-17 17:15 ` Tejun Heo
2015-09-17 17:58 ` James Bottomley
2015-09-17 18:00 ` Tejun Heo
2015-09-17 0:29 ` [PATCH 2/2] remoteproc: fix memory leak of remoteproc ida cache layers Suman Anna
2015-11-26 9:38 ` Ohad Ben-Cohen
2015-11-26 10:37 ` Michael S. Tsirkin
2015-11-26 15:47 ` Ohad Ben-Cohen
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=20150917151026.GB7205@mtj.duckdns.org \
--to=htejun@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ohad@wizery.com \
--cc=open-iscsi@googlegroups.com \
--cc=s-anna@ti.com \
--cc=virtualization@lists.linux-foundation.org \
/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
all inboxes | Powered by JetHome®