[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-IPTables-libiptc-0.52- |perl-IPTables-libiptc-0.52- |28.fc30 |28.fc30 |perl-IPTables-libiptc-0.52- |perl-IPTables-libiptc-0.52- |26.fc28 |26.fc28 ||perl-IPTables-libiptc-0.52- ||28.fc29 --- Comment #9 from Fedora Update System --- perl-IPTables-libiptc-0.52-28.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-IPTables-libiptc-0.52- |perl-IPTables-libiptc-0.52- |28.fc30 |28.fc30 ||perl-IPTables-libiptc-0.52- ||26.fc28 Resolution|--- |ERRATA Last Closed||2019-02-08 02:29:30 --- Comment #8 from Fedora Update System --- perl-IPTables-libiptc-0.52-26.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 --- Comment #7 from Fedora Update System --- perl-IPTables-libiptc-0.52-26.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c60748c7fb -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #6 from Fedora Update System --- perl-IPTables-libiptc-0.52-28.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-f0bf1ecc73 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 --- Comment #5 from balwi...@gmail.com --- Installed perl-IPTables-libiptc-0.52-28.fc29. Tested. No lockfile is being created and there is no wait. It works for me. Thank you. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 --- Comment #4 from balwi...@gmail.com --- Yes, you are right about the upstream. Fedora was bundling patching it with increasing versions of bundled iptables, so I wondered that it might be enough to continue this with iptables 1.8. Currently there is a version mismatch in the bundled version (1.6.1) and the system one. Yes, the perl module is ignorant about locking. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 --- Comment #3 from Fedora Update System --- perl-IPTables-libiptc-0.52-26.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c60748c7fb -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 --- Comment #2 from Fedora Update System --- perl-IPTables-libiptc-0.52-28.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f0bf1ecc73 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-IPTables-libiptc-0.52- ||28.fc30 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Petr Pisar --- 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. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1670047] perl-IPTables-libiptc-0.52-27.fc29: upon script completion xtables.lock is not removed; multiple calls of IPTables::libiptc::iptables_do_command() result in an infinite wait loop
https://bugzilla.redhat.com/show_bug.cgi?id=1670047 balwi...@gmail.com changed: What|Removed |Added Summary|upon script completion |perl-IPTables-libiptc-0.52- |xtables.lock is not |27.fc29: upon script |removed; multiple calls of |completion xtables.lock is |IPTables::libiptc::iptables |not removed; multiple calls |_do_command() result in an |of |infinite wait loop |IPTables::libiptc::iptables ||_do_command() result in an ||infinite wait loop -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
