Re: Kill IFAFREE()

2013-03-06 Thread Martin Pieuchot
On 05/03/13(Tue) 21:57, Claudio Jeker wrote: On Tue, Mar 05, 2013 at 12:03:49PM +0100, Mike Belopuhov wrote: On 5 March 2013 11:55, Mark Kettenis mark.kette...@xs4all.nl wrote: Date: Tue, 5 Mar 2013 11:36:36 +0100 From: Martin Pieuchot mpieuc...@nolizard.org The ifaddr structure

Re: Kill IFAFREE()

2013-03-06 Thread Kenneth R Westerback
On Wed, Mar 06, 2013 at 03:58:22PM +0100, Mark Kettenis wrote: Date: Wed, 6 Mar 2013 15:25:34 +0100 From: Martin Pieuchot mpieuc...@nolizard.org On 05/03/13(Tue) 21:57, Claudio Jeker wrote: On Tue, Mar 05, 2013 at 12:03:49PM +0100, Mike Belopuhov wrote: On 5 March 2013 11:55, Mark

Kill IFAFREE()

2013-03-05 Thread Martin Pieuchot
The ifaddr structure contains a reference counter and two different way to check it before freeing its memory: a macro IFAFREE(), and a function ifafree(). Because the former calls the latter when the reference counter is null, and then also check for the reference counter, I see no point in

Re: Kill IFAFREE()

2013-03-05 Thread Mike Belopuhov
On 5 March 2013 11:55, Mark Kettenis mark.kette...@xs4all.nl wrote: Date: Tue, 5 Mar 2013 11:36:36 +0100 From: Martin Pieuchot mpieuc...@nolizard.org The ifaddr structure contains a reference counter and two different way to check it before freeing its memory: a macro IFAFREE(), and a