[Bug 427629] named stops responding if it cannot communicate over IPSEC

Mon May 19 12:04:08 UTC 2008

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: named stops responding if it cannot communicate over IPSEC

https://bugzilla.redhat.com/show_bug.cgi?id=427629

atkac at redhat.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|7                           |rawhide

------- Additional Comments From atkac at redhat.com  2008-05-19 08:04 EST -------
Hm, from lkml it seems that network maintainer thinks current state is correct
(http://lkml.org/lkml/2007/12/4/260). But I (and also upstream developers) think
that if socket is marked as non blocking it should not block.

In my opinion xfrm_larval_drop should be dropped because if someone marks socket
as non blocking he has reasons for it. Or at least set it to "1" by default.
Other kernels (FreeBSD I think) doesn't suffer from this feature.

I can create patch which sets xfrm_larval_drop to "1" when bind starts but it is
nasty hack and only hides original problem. Could someone from our kernel guys
try persuade Dave Miller to set xfrm_larval_drop to 1 by default, please? Thanks

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.