[asterisk-bugs] [Asterisk 0017450]: [patch] "setvar" can add multiple variables with the same name to a channel, and has a mismatch between his behaviour and his do

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17450 
====================================================================== 
Reported By:                nahuelgreco
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17450
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     confirmed
Asterisk Version:           SVN 
JIRA:                       SWP-1635 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 267095 
Request Review:              
====================================================================== 
Date Submitted:             2010-06-02 17:28 CDT
Last Modified:              2011-04-08 15:30 CDT
====================================================================== 
Summary:                    [patch] "setvar" can add multiple variables with the
same name to a channel, and has a mismatch between his behaviour and his do
Description: 
Suppose the following piece of chan_dahdi.conf:

  setvar=V1=foo
  channel => 1

  setvar=V2=bar
  channel => 2

  setvar=V1=baz
  channel => 3

In the current trunk version, each channel (dahdi_pvt structure) will have
his own copies of the variables (after
https://issues.asterisk.org/view.php?id=16359 fix). For example, the
ast_variables linked list for channel 3 will have the following form:

  channel 3:   V1=foo -> V2=bar -> V1=baz

When a call is made and dahdi_new(...) is executed, dahdi_new(...) will
processes the variables list left-to-right, so for a call in channel 3 the
value of V1 for that call will be finally "baz" because is the last one to
be set by dahdi_new(...). This makes the bug benevolous, the call variables
will be ok, but if you do a "dahdi show channel 3" you will see the two
versions of V1, and that's wrong. Before the
https://issues.asterisk.org/view.php?id=16359 fix the bug was worse,
because the call in channel 3 got V1=foo.

A patch against trunk removing the duplicates is attached.

Also, there is a conceptual mismatch. The documentation in
chan_dahdi.conf.sample states that "setvar" defines a "Channel variable to
be set for all calls from this channel". Maybe the correct behaviour is to
get only V1 defined for channel 3 and not V2, by resetting the setvar list
(confp->chan.vars) after each "channel" statement. 

I also think the linked list built at confp->chan.vars is probably leaking
across reloads.

====================================================================== 

---------------------------------------------------------------------- 
 (0133556) jrose (manager) - 2011-04-08 15:30
 https://issues.asterisk.org/view.php?id=17450#c133556 
---------------------------------------------------------------------- 
reload chan_dahdi doesn't leak any memory and according to a few of our
devs, the way variables get stored in the pvt struct like that is fine
since once it reaches the status of being a channel there is really only
one variable for each name anyway.  I'm closing this issue.  If there is
some specific memory leak that you can demonstrate with malloc_debug
(memory show summary), please create a new issue so that we can investigate
it more thoroughly. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-08 15:30 jrose          Note Added: 0133556                          
======================================================================