From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@free.fr>
Subject: Re: Re: [multipath 1/1] cache sysfs_devices
Date: Tue, 24 Jul 2007 08:35:16 +0200 [thread overview]
Message-ID: <46A59DA4.1010703@suse.de> (raw)
In-Reply-To: <20070720210343.GA11879@bogon.ms20.nix>
Guido Guenther wrote:
> I give up on git-send-email - it always fools me. Nevertheless this one
> fixes the described bug of paths coming back as different block
> devices:
>
> Keep a list of sysfs devices for sysfs_device_get() so uev_trigger() can look
> up the necessary information for proper path removal in case of a 'remove'
> uevent - the sysfs files in the filesystem might be long gone at this point.
>
> This also plugs a memory leak where we'd malloc space for the same sysfs device
> over and over again for every processed uevent.
>
Hmm. But now we're running into the opposite trap: memory for a block device once
existing will never be freed. So over time we're likely to become a memory hog.
Better it would be to remove the sysfs device from the cache once we're done
with it.
I'll cook up a patch.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2007-07-24 6:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 22:54 multipath-tools causes path to come back as different block device Brian De Wolf
2007-07-20 7:24 ` Hannes Reinecke
2007-07-20 11:53 ` Guido Guenther
2007-07-20 14:40 ` Hannes Reinecke
2007-07-20 17:29 ` Guido Guenther
2007-07-20 20:52 ` [multipath 1/1] cache sysfs_devices -s
[not found] ` <11849647793576-git-send-email--s>
2007-07-20 21:03 ` Guido Guenther
2007-07-20 22:18 ` Christophe Varoqui
2007-07-24 6:35 ` Hannes Reinecke [this message]
2007-07-25 16:37 ` Guido Guenther
2007-07-20 17:05 ` multipath-tools causes path to come back as different block device Brian De Wolf
2007-07-20 10:10 ` Guido Guenther
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=46A59DA4.1010703@suse.de \
--to=hare@suse.de \
--cc=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.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.