BIND 10 #533: additional regression in msgq with kqueue
BIND 10 Development
do-not-reply at isc.org
Wed Jan 26 19:24:30 UTC 2011
#533: additional regression in msgq with kqueue
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner: UnAssigned
Type: defect | Status: reviewing
Priority: | Milestone: feature
critical | backlog item
Component: msgq | Resolution:
Keywords: | Sensitive: 0
Estimated Number of Hours: 0.0 | Add Hours to Ticket: 0
Billable?: 1 | Total Hours: 0
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:3 vorner]:
> This fails on linux:
[snip]
> That is the reason why I didn't use the default parameter, but the
boolean flag. If it is only in the code, the constant is not needed until
it is used, but this way it is needed at the load of the module.
Ah, I see. I've created a branch and committed and pushed the proposed
fix
with addressing this issue. I confirmed it worked on both MacOS and
bind10.isc.org (Linux). Please check.
> Maybe I got it wrong how the events in kqueue work, but if there's an
event with the same id (fd), isn't the older one completely replaced by
the new one? By the patch you sent, it seems not.
No, kqueue events are identified by a pair "ident(=FD), filter". From
kqueue(2):
The filter identified in a kevent is executed upon the initial
registration of that event in order to detect whether a
preexisting condition is present, and is also executed whenever
an event is passed to the filter for evalua- tion. If the filter
determines that the condition should be reported, then the kevent
is placed on the kqueue for the user to retrieve.
--
Ticket URL: <http://bind10.isc.org/ticket/533#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list