bind dies with assertion failure

[Oscar Ricardo Silva]

I *THINK* I found the reason for why we're exposed to this bug ... It 
would appear that Redhat based their BIND package on 9.8.2rc1.  Guess 
where the patch for this bug was applied?  9.8.2rc2.



Oscar


On 07/02/2012 05:47 PM, Evan Hunt wrote:
> I can't answer for RedHat, but this bug fix was included in BIND 9.8.2.
>
> 3284.   [bug]           Address race conditions with the handling of
>                          rbtnode.deadlink. [RT #27738]
>
> On Mon, Jul 02, 2012 at 05:40:51PM -0500, Oscar Ricardo Silva wrote:
>> I may have missed something but has this been patched in a 9.8.x version
>> of BIND?  According to the 9.9.0 release notes this has been addressed
>> but just wondering about the availability for other vulnerable versions.
>>   Also, is there a known trigger?
>>
>> The reason I'm running is that we're currently running the stock version
>> of BIND available with RHEL6.  It's their policy to backport patches and
>> if there's a patch available then they may apply it faster rather than
>> deploying a new version.
>>
>>> It is a known issue, and is indeed a bug.  We're working on it already, so
>>> stay tuned.
>>>
>>> --Michael
>>>
>>> On Feb 14, 2012, at 12:44 PM, Alex wrote:
>>>
>>>>> Hi,
>>>>>
>>>>> I have a fedora16 x86_64 box and named keeps dying with an assertion
>>>> failure:
>>>>>
>>>>> 14-Feb-2012 13:24:41.137 general: critical: rbtdb.c:1619:
>>>>> INSIST(!((void *)((node)->deadlink.prev) != (void *)(-1))) failed
>>>>> 14-Feb-2012 13:24:41.137 general: critical: exiting (due to assertion
>>>> failure)
>>>>>
>>>>> This is bind-9.8.2-0.2.rc1.fc16.x86_64. Is this a known issue? Is this
>>>>> indeed a bug or perhaps something otherwise wrong with the server?
>>>>>
>>>>> How can I troubleshoot this further?
>>>>>
>>>>> Thanks,
>>>>> Alex
>