diff options
| author | Peter Rajnoha <prajnoha@redhat.com> | 2012-08-27 14:19:30 +0200 |
|---|---|---|
| committer | Peter Rajnoha <prajnoha@redhat.com> | 2012-08-27 14:33:54 +0200 |
| commit | 847e2856a29c41756cc5bbaf70eb87ea030826f4 (patch) | |
| tree | a82ac80008113d42162368d406312040cedc10f3 /WHATS_NEW_DM | |
| parent | 2a70e98b05603bf8fc59929fd2709fb5d2b859e6 (diff) | |
| download | lvm2-847e2856a29c41756cc5bbaf70eb87ea030826f4.tar.gz lvm2-847e2856a29c41756cc5bbaf70eb87ea030826f4.tar.xz lvm2-847e2856a29c41756cc5bbaf70eb87ea030826f4.zip | |
config: require dm_config_create_value for dm_config_node's value
If we were defining a section (which is a node without a value) and
the value was created automatically on dm_config_create_node call,
we were wasting resources as the next step after creating the config
node itself was assigning NULL for the node's value.
The dm_config_node_create + dm_config_create_value sequence should be
used instead for settings and dm_config_node_create alone for sections.
The majority of the code already used the correct sequence. Though
with dm_config_node_create fn creating the value as well, the pool
memory was being trashed this way.
This patch removes the node value initialization on dm_config_create_node
fn call and keeps it for the direct dm_config_create_value fn call.
Diffstat (limited to 'WHATS_NEW_DM')
| -rw-r--r-- | WHATS_NEW_DM | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/WHATS_NEW_DM b/WHATS_NEW_DM index d0e8f7df..c46db61e 100644 --- a/WHATS_NEW_DM +++ b/WHATS_NEW_DM @@ -1,5 +1,6 @@ Version 1.02.77 - ================================= + Don't create value for dm_config_node and require dm_config_create_value call. Check for existing new_name for dmsetup rename. Fix memory leak in dmsetup _get_split_name() error path. |