[asterisk-dev] [Code Review] handle DAHDI_EVENT_REMOVED on a D-Channel

[Jeff Peeler]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/726/#review2232
-----------------------------------------------------------



/trunk/channels/chan_dahdi.c
<https://reviewboard.asterisk.org/r/726/#comment4735>

    I don't think issuing a pthread_cancel will terminate the thread immediately, you must join before you can safely start closing fds. See how dahdi_restart is done.



/trunk/channels/chan_dahdi.c
<https://reviewboard.asterisk.org/r/726/#comment4737>

    I can't see why anyone would want to shut down the span, but keep the associated b-channels. At this point you could just lock the iflock and call destroy_channel on every dahdi_pvt via the sig_pri_chan pvts. 


- Jeff


On 2010-06-16 15:15:17, Tzafrir Cohen wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/726/
> -----------------------------------------------------------
> 
> (Updated 2010-06-16 15:15:17)
> 
> 
> Review request for Asterisk Developers and rmudgett.
> 
> 
> Summary
> -------
> 
> When a DAHDI device is removed at run-time it sends the event DAHDI_EVENT_REMOVED on each channel. This is intended to signal the userspace program to close the respective file handle, as the driver of the device will need all of them closed to properly clean-up.
> 
> This event has long since been handled in chan_dahdi (chan_zap at the time). However the event that is sent on a D-Channel of a "PRI" (ISDN) span simply gets ignored.
> 
> This code adds handling for closing the file descriptor (and shutting down the span, while we're at it). It also adds a CLI command to help test it.
> 
> This code seems to be rather DAHDI-generic and thus I opted not to change anything in sig_pri.c .
> 
> I use a simplified version of the container_of() macro from the Linux Kernel, which basically returns a pointer to a struct that contains a different struct to which we already have a pointer. Thus I assume this will always be run with on a struct sig_pri_pri that is contained ina s struct dahdi_pri .
> 
> I'm not sure what proper locking needs doing.
> 
> 
> Diffs
> -----
> 
>   /trunk/channels/chan_dahdi.c 270972 
> 
> Diff: https://reviewboard.asterisk.org/r/726/diff
> 
> 
> Testing
> -------
> 
> Disconnecting either using the CLI command or with device removal for some E1 and some BRI devices.
> 
> 
> Thanks,
> 
> Tzafrir
> 
>