https://bugzilla.redhat.com/show_bug.cgi?id=1670047
Petr Pisar <ppisar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #1 from Petr Pisar <ppisar(a)redhat.com> ---
I wonder that the Perl worked so far. Upstream was unable to provide any fix in
last 8 years and claimed guilty iptables upstream that it does not provide a
library. iptables upstream postponed making the library as the people moved to
firewalld and nftables.
If I recall correctly, iptables 1.6 did not perform locking correctly and did
not enforce it. Perl module never bothered with any locking. It seems that the
recent iptables changed the locking. Not only they force it, they also make it
difficult for use as a library. E.g. the locking subroutine exits current
program if it times out. This is unacceptable for the Perl module.
Reading the code it seems as iptables's do_command4() obtained another argument
for enforcing the locking and the Perl module does not specify it. If I disable
locking, it works. I think this is the easiest fix without a risk of exiting a
program.
--
You are receiving this mail because:
You are on the CC list for the bug.